Certificats Let's Encrypt
Find a file
2012-08-10 16:26:25 -07:00
client-webserver rename function and add sanity-checking assertion 2012-08-09 23:38:46 -07:00
doc Docs 2012-05-17 13:08:39 -07:00
m3crypto@c63d9b1b36 Disable raw IPv6 addresses by default 2012-08-06 15:27:05 -07:00
sample-files weak Debian keys, via http://certlogik.com/debian-weak-key-check/ 2012-07-17 00:19:08 -07:00
server-ca evidently, current best practice is to include ALL DNS names, including the primary name, as SANs 2012-08-10 16:26:25 -07:00
.gitignore some .gitignore files to suppress display of generated files in git 2012-07-14 13:49:58 -07:00
.gitmodules Add m3crypto as a submodule 2012-07-10 18:04:18 -07:00
README now there is a dependency on python-dialog 2012-08-09 16:36:52 -07:00

The Chocolate project to implement sweet automatic encryption for webservers.

There are two portions to the Chocoate protocol.

client-webserver/ contains code that can be run on any webserver (eventually,
email, XMPP and other SSL-securable servers too); it is used to automatically
request and install a CA-signed certificate for that server's public names.

server-ca/ contains a reference implementation for CAs to receive requests for
certs, set challenges for the requesting servers to prove that they really
control the names, and issue certificates.

Debian dependencies:

build deps:
swig
protobuf-compiler
python-dev

others:
gnutls-bin # for make cert requests
python-protobuf
python-dialog
hashcash