No description
Find a file
2014-06-05 18:45:03 -07:00
acip First import of ACIP draft 2014-02-05 13:39:26 -08:00
doc tweaks 2013-08-11 17:48:24 +02:00
m3crypto@c63d9b1b36 Disable raw IPv6 addresses by default 2012-08-06 15:27:05 -07:00
pygeoip@2bd928e6b3 and my cached-consensus exit geography parser 2012-08-31 11:42:29 -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 per discussion, remove clock skew checks; also, two TODOs moved to filed issues 2012-11-19 11:59:21 -08:00
trustify working demonstration of proof-of-possession logic 2013-10-23 18:56:25 -07:00
.gitignore Move protocol and client into Python modules 2012-08-12 07:49:45 +03:00
.gitmodules and my cached-consensus exit geography parser 2012-08-31 11:42:29 -07:00
MANIFEST.in Add setuptools-based setup.py & MANIFEST.in 2012-08-12 09:03:13 +03:00
popchallenge.py per ENISA report, switched to PKCS#1 PSS signature method 2013-10-31 12:39:00 -07:00
popchallenge_demo.py in demo, only do POP challenge if the challenge type is POP challenge 2013-10-31 12:37:44 -07:00
README Update README 2014-06-05 18:45:03 -07:00
setup.py Add setuptools-based setup.py & MANIFEST.in 2012-08-12 09:03:13 +03:00
trustify.py Added restart to rollback call 2013-05-23 22:11:15 -04:00

The Chocolate project to implement sweet automatic encryption for webservers.

There are two portions to the Chocolate protocol.

trustify/ 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