certbot/server-ca
2012-07-14 15:02:26 -07:00
..
demoCA some .gitignore files to suppress display of generated files in git 2012-07-14 13:49:58 -07:00
sni_challenge some .gitignore files to suppress display of generated files in git 2012-07-14 13:49:58 -07:00
.gitignore some .gitignore files to suppress display of generated files in git 2012-07-14 13:49:58 -07:00
CA.sh correctly emit subject alternative names and remove most user-supplied data from cert 2012-07-13 22:50:58 -07:00
chocolate.py use hashcash in protocol 2012-07-14 14:34:24 -07:00
chocolate_protocol.proto remove disused debug flag in protocol 2012-07-09 22:33:02 -07:00
clear-db.py script for clearing out Redis databae 2012-07-12 16:29:54 -07:00
CSR.py notes on locking and concurrency 2012-07-14 14:56:19 -07:00
daemon.py switch to hashlib 2012-07-14 15:02:26 -07:00
hashcash.py use hashcash in protocol 2012-07-14 14:34:24 -07:00
Makefile we're using git pull rather than scp/rsync to deploy now 2012-07-14 14:56:30 -07:00
README update description of dependencies and deployment 2012-07-13 16:03:21 -07:00
REDIS moving everything server-side to server-ca directory 2012-07-06 14:45:26 -07:00

In this directory is a reference CA implementation of the Chocolate protocol,
DV and signing mechanism.

Instead of using "make deploy", we're currently using git pull to deploy this.
This requires restarting lighttpd on the server and ensuring that Redis and
a copy of daemon.py are running there.  If the .proto definition has
changed, it also needs to be recompiled on both the server and the client.



chocolate.py - server-side, requires web.py (python-webpy),
        PyCrypto (python-crypto) 2.3 (not 2.1!!), redis, python-redis,
        python-protobuf, "M3Crypto" (from our own tree) (hence also
	build-essential, python-dev, and swig)
	probably wants to run under a web server like lighttpd with fastcgi


chocolate_protocol.proto - protocol definition; needs protobuf-compiler

sni_challenge -
	Assumes Apache server with name based virtual hosts is running 
	(for intended address).
	Call perform_sni_cert_challenge(address, r, nonce) to do the whole 
	challenge.
	Example code is given in main method
	Right now requires full path specification of CSR/KEY in the Global 
	Variables (how should this be specified?)