This is an implementation of an ACME-based CA. The ACME protocol allows the CA to automatically verify that an applicant for a certificate actually controls an identifier, and allows domain holders to issue and revoke certificates for their domains.
Boulder has a Dockerfile to make it easy to install and set up all its dependencies. This approach is most suitable if you just need to set up Boulder for the purpose of testing client software against it. To start Boulder in a Docker container, run:
./test/run-docker.sh
This approach is better if you intend to develop on Boulder frequently, because it's challenging to develop inside the Docker container.
We recommend setting git's fsckObjects setting for better integrity guarantees when getting updates.
Boulder requires an installation of RabbitMQ, libtool-ltdl, goose, and MariaDB 10 to work correctly. On Ubuntu and CentOS, you may have to install RabbitMQ from https://rabbitmq.com/download.html to get a recent version.
Also, Boulder requires Go 1.5. As of September 2015 this version is not yet
available in OS repositories, so you will have to install from https://golang.org/dl/.
Add ${GOPATH}/bin to your path.
Ubuntu:
sudo apt-get install libltdl3-dev mariadb-server rabbitmq-server
CentOS:
sudo yum install libtool-ltdl-devel MariaDB-server MariaDB-client rabbitmq-server
Arch Linux:
sudo pacman -S libtool mariadb rabbitmq --needed
OS X:
brew install libtool mariadb rabbitmq
or
sudo port install libtool mariadb-server rabbitmq-server
(On OS X, using port, you will have to add CGO_CFLAGS="-I/opt/local/include" CGO_LDFLAGS="-L/opt/local/lib" to your environment or go invocations.)
Resolve Go-dependencies, set up a database and RabbitMQ:
./test/setup.sh
Note: setup.sh calls create_db.sh, which uses the root MariaDB
user with the default password, so if you have disabled that account
or changed the password you may have to adjust the file or recreate the commands.
Start each boulder component with test configs (Ctrl-C kills all):
./start.py
Run tests:
./test.sh
Working with a client:
Check out the official Let's Encrypt client from https://github.com/letsencrypt/letsencrypt/ and follow the setup instructions there. Once you've got the client set up, you'll probably want to run it against your local Boulder. There are a number of command line flags that are necessary to run the client against a local Boulder, and without root access. The simplest way to run the client locally is to source a file that provides an alias for letsencrypt that has all those flags:
source ~/letsencrypt/tests/integration/_common.sh
letsencrypt_test certonly -a standalone -d example.com
Your local Boulder instance uses a fake DNS server that returns 127.0.0.1 for any query, so you can use any value for the -d flag.
The CA is divided into the following main components:
- Web Front End
- Registration Authority
- Validation Authority
- Certificate Authority
- Storage Authority
This component model lets us separate the function of the CA by security context. The Web Front End and Validation Authority need access to the Internet, which puts them at greater risk of compromise. The Registration Authority can live without Internet connectivity, but still needs to talk to the Web Front End and Validation Authority. The Certificate Authority need only receive instructions from the Registration Authority.
client <--ACME--> WFE ---+
. |
. +--- RA --- CA
. |
client <-checks-> VA ---+
Internally, the logic of the system is based around four types of objects: registrations, authorizations, challenges, and certificates, mapping directly to the resources of the same name in ACME.
Requests from ACME clients result in new objects and changes to objects. The Storage Authority maintains persistent copies of the current set of objects.
Objects are also passed from one component to another on change events. For example, when a client provides a successful response to a validation challenge, it results in a change to the corresponding validation object. The Validation Authority forwards the new validation object to the Storage Authority for storage, and to the Registration Authority for any updates to a related Authorization object.
Boulder uses AMQP as a message bus. For components that you want to be remote, it is necessary to instantiate a "client" and "server" for that component. The client implements the component's Go interface, while the server has the actual logic for the component. More details in amqp-rpc.go.
The full details of how the various ACME operations happen in Boulder are laid out in DESIGN.md
All Go dependencies are vendored under the Godeps directory, to make dependency management easier.
Local development also requires a RabbitMQ installation and MariaDB 10 installation (see above). MariaDB should be run on port 3306 for the default integration tests.
To update the Go dependencies:
# Fetch godep
go get -u github.com/tools/godep
# Check out the currently vendorized version of each dependency.
godep restore
# Update to the latest version of a dependency. Alternately you can cd to the
# directory under GOPATH and check out a specific revision. Here's an example
# using cfssl:
go get -u github.com/cloudflare/cfssl/...
# Update the Godep config to the appropriate version.
godep update github.com/cloudflare/cfssl/...
# Save the dependencies, rewriting any internal or external dependencies that
# may have been added.
godep save -r ./...
git add Godeps
git commit