1
0
mirror of https://github.com/certbot/certbot.git synced 2026-01-26 07:41:33 +03:00
Files
certbot/server-ca
2012-11-18 22:19:18 -08:00
..
2012-10-18 17:20:59 -07:00
2012-11-18 22:12:00 -08:00
2012-11-18 20:56:58 -08:00
2012-11-18 20:53:18 -08:00
2012-10-17 18:36:24 -07:00
2012-10-08 18:05:02 -07:00
2012-10-17 18:36:24 -07:00
2012-10-17 18:36:24 -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

daemons/{makechallenge,testchallenge,issue,logging}-daemon.py -
        daemons to handle back-end implementation of protocol state transitions

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 verify the 
	server.
	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?)
        requires python-socksipy, tor