certificate-transparency

README

certificate-transparency

Auditing for TLS certificates.

Quickstart on Ubuntu

The following steps will checkout the code and build it on a clean Ubuntu 14.04 LTS installation. It has also been tested on an Ubuntu 15.04 installation.

First, install packaged dependencies:

sudo apt-get update -qq
sudo apt-get install -qq unzip cmake g++ libevent-dev golang-go autoconf pkg-config \
    libjson-c-dev libgflags-dev libgoogle-glog-dev libprotobuf-dev libleveldb-dev \
    libssl-dev libgoogle-perftools-dev protobuf-compiler libsqlite3-dev ant openjdk-7-jdk \
    libprotobuf-java python-gflags python-protobuf python-ecdsa python-mock \
    python-httplib2 git libldns-dev

Next, we need libevhtp version 1.2.10 which is not packaged in Ubuntu yet, so we build from source:

wget https://github.com/ellzey/libevhtp/archive/1.2.10.zip
unzip 1.2.10.zip
cd libevhtp-1.2.10/
cmake -DEVHTP_DISABLE_REGEX:STRING=ON -DCMAKE_C_FLAGS:STRING=-fPIC .
make
cd ..

And let's get our own Google Test / Google Mock as these vary in incompatible ways between packaged releases:

wget https://googlemock.googlecode.com/files/gmock-1.7.0.zip
unzip gmock-1.7.0.zip

Now, clone the CT repo:

git clone https://github.com/google/certificate-transparency.git
cd certificate-transparency/

One-time setup for Go:

export GOPATH=$PWD/go
mkdir -p $GOPATH/src/github.com/google
ln -s $PWD $GOPATH/src/github.com/google
go get -v -d ./...

Build CT server C++ code:

./autogen.sh
./configure GTEST_DIR=../gmock-1.7.0/gtest GMOCK_DIR=../gmock-1.7.0 \
    CPPFLAGS="-I../libevhtp-1.2.10 -I../libevhtp-1.2.10/evthr \
    -I../libevhtp-1.2.10/htparse" LDFLAGS=-L../libevhtp-1.2.10
make check

Build and test Java code:

ant build test

Build and test Python code:

make -C python test

Best and test Go code:

go test -v ./go/...

Dependencies

• A working C++11 compiler.

• autoconf/automake etc.

• cmake

• git

• GNU make

• libtool

• shtool

• Tcl

• pkgconf

• python27

• depot_tools

Building with gclient

This is the recommended method for all platforms as it gives you a reproducible build.

Known to work on FreeBSD 10, OS X (10.10) [tested with XCode + brew installation of above deps], and Ubuntu 14.04.

mkdir ct  # or whatever directory you prefer
cd ct
gclient config --name="certificate-transparency" git@github.com:google/certificate-transparency.git
gclient sync
# substitute gmake or gnumake below if that's that your platform calls it:
make -C certificate-transparency check

If you're trying to clone from a branch on the CT repo then you'll need to substitute the following command for the gclient config command above, replacing branch as appropriate

gclient config --name="certificate-transparency" git@github.com:google/certificate-transparency.git@branch

To run any of the built binaries you'll need to:

export LD_LIBRARY_PATH=/path/to/ct/install/lib'

Old Method

• OpenSSL, at least 1.0.0q, preferably 1.0.1l or 1.0.2 (and up)

The checking of SCTs included in the RFC 6962 TLS extension is only included in OpenSSL 1.0.2. As of this writing, this version is not yet released, so this means hand building the OpenSSL_1_0_2-stable branch from the OpenSSL git repository.

• googlemock (tested with 1.7.0)

Gmock provides a bundled version of gtest, which will also be used.

Unpack googlemock, but do not build it. Upstream recommends to build a new copy from source for each package to be tested. We follow this advice in our Makefile, which builds gmock/gtest automatically.

Some systems make the googlemock source available as a package; on Debian, this is in the google-mock package, which puts it in /usr/src/gmock. Our Makefile looks in that location by default, but if your googlemock sources are in a different location, set the GMOCK_DIR environment variable to point at them.

If you are on FreeBSD, you may need to apply the patch in gtest.patch to the gtest subdirectory of gmock.

• protobuf (tested with 2.5.0)
• gflags (tested with 1.6 and 2.0)
• glog (tested with 0.3.1)

Make sure to install glog after gflags, to avoid linking errors.

• sqlite3
• leveldb
• JSON-C, at least 0.11

You can specify a JSON-C library in a non-standard location using the JSONCLIBDIR environment variable. Version 0.10 would work as well, except the json_object_iterator.h header is not properly copied when installing. If you can install the missing header manually, it should work.

• libevent (tested with 2.0.21-stable)
• libevhtp (tested with 1.2.10) If building libevhtp from source, you may need to disable the regex support with the following cmake flag: -DEVHTP_DISABLE_REGEX:STRING=ON

You can specify a non-installed locally built library using the LIBEVENTDIR environment variable to point to the local build. Note that the FreeBSD port version 2.0.21_2 does not appear to work correctly (it only listens on IPv6 for the HTTP server) - for that platform we had to build from the source, specifically commit 6dba1694c89119c44cef03528945e5a5978ab43a.

• ldns
• ant
• Python libraries:
• pyasn1 and pyasn1-modules (optional, needed for upload_server_cert.sh)
• dnspython

Building

You can build the log server with the following commands:

$ ./autogen.sh  # only necessary if you're building from git
$ ./configure
$ make

You can give the configure script extra parameters, to set compilation flags, or point to custom versions of some dependencies (notably, googlemock often needs this). For example, to compile with Clang, using googlemock in $HOME/gmock, and a custom libevent in $HOME/libevent:

$ ./configure CXX=clang++ GMOCK_DIR=$HOME CPPFLAGS="-I$HOME/libevent/include" LDFLAGS="-L$HOME/libevent/.libs"

Running ./configure --help provides more information about various variables that can be set.

Running Unit Tests

Run unit tests with this command

$ make check

If the build still fails because of missing libraries, you may need to set the environment variable LD_LIBRARY_PATH. On Linux, if you did not change the default installation path (such as /usr/local/lib), running

$ ldconfig

or, if needed,

$ sudo ldconfig

should resolve the problem.

End-To-End Tests

For end-to-end server-client tests, you will need to install Apache and point the tests to it. See test/README for how to do so.

Testing and Logging Options

Note that several tests write files on disk. The default directory for storing temporary testdata is /tmp. You can change this by setting TMPDIR=<tmpdir> for make.

End-to-end tests also create temporary certificate and server files in test/tmp. All these files are cleaned up after a successful test run.

For logging options, see http://google-glog.googlecode.com/svn/trunk/doc/glog.html

By default, unit tests log to stderr, and log only messages with a FATAL level (i.e., those that result in abnormal program termination). You can override the defaults with command-line flags.

End-to-end tests log everything at INFO level and above.