From 42f014c49a3a5e4356c559d92dd763c64e3722b5 Mon Sep 17 00:00:00 2001
From: Jeff Trawick
Experimental support for this is implemented in the ctauditscts
- command (in the httpd source tree, not currently installed), which itself
- relies on the verify_single_proof.py
tool in the
+ command, which itself relies on the verify_single_proof.py
tool in the
certificate-transparency open source project. ctauditscts
can parse data for off-line audit (enabled with the
CTAuditStorage
directive) and invoke verify_single_proof.py
.
- However, verify_single_proof.py
is not complete currently and does
- not provide a way to identify audit failures.
Here are rough notes for using ctauditscts
:
PYTHONPATH
to include the src/python
+ requirements.txt
file
+ from the certificate-transparency project and run the following steps
+ with that virtualenv activated.PYTHONPATH
to include the python
directory within the certificate-transparency tools.PATH
to include the src/python/ct/client/tools
+ PATH
to include the python/ct/client/tools
directory.ctauditscts
, passing the value of the
CTAuditStorage
directive and, optionally, the path to
@@ -273,7 +277,7 @@ testing.
The data saved for audit can also be used by other programs; refer to the
- ctauditscts
source code for details.
ctauditscts
source code for details on processing the data.
executable is the full path to the log client tool, which is
- normally file src/client/ct
within the source tree of the
+ normally file cpp/client/ct
(or ct.exe
) within the
+ source tree of the
certificate-transparency open source project.
If this directive is not configured, server certificates cannot be submitted to logs in order to obtain SCTs; thus, only admin-managed - SCTs will be provided to clients.
+ SCTs or SCTs in certificate extensions will be provided to clients.