certbot/server-ca
2012-07-10 16:17:10 -04:00
..
demoCA changes to make CSR.issue() successfully issue certs 2012-07-09 00:01:19 -07:00
sni_challenge Fixed conference call bug, made challenge servers only accessible by SNI name 2012-07-10 16:17:10 -04:00
CA.sh changes to make CSR.issue() successfully issue certs 2012-07-09 00:01:19 -07:00
chocolate.py moving everything server-side to server-ca directory 2012-07-06 14:45:26 -07:00
chocolate_protocol.proto moving everything server-side to server-ca directory 2012-07-06 14:45:26 -07:00
CSR.py changes to make CSR.issue() successfully issue certs 2012-07-09 00:01:19 -07:00
daemon.py moving everything server-side to server-ca directory 2012-07-06 14:45:26 -07:00
Makefile moving everything server-side to server-ca directory 2012-07-06 14:45:26 -07:00
pkcs10.py moving everything server-side to server-ca directory 2012-07-06 14:45:26 -07:00
README moving everything server-side to server-ca directory 2012-07-06 14:45:26 -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.

Set CHOCOLATESERVER environment variable for "make deploy"!


chocolate.py - server-side, requires web.py (python-webpy),
        PyCrypto (python-crypto) 2.3 (not 2.1!!), redis, python-redis,
        python-protobuf, python-nss
	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?)