|  | Commit message (Collapse) | Author | Age | Files | Lines | 
|---|
| | 
| 
| 
| 
| 
| | ChecksumV1 entries can be submitted using client-side ed25519
signatures.  The resulting SignedDebugInfoV1 is then verified using the
log's announced signature scheme and public key (currently only ed25519). | 
| | 
| 
| 
| | A collection of immutable log parameters, see documentation. | 
| | 
| 
| 
| 
| 
| | Structured files a bit better, added more documentation, switched to
pointers as default (unless specifically motivated not to do so), and
encapsulated TLS (un)marshaling for the respective types that use it. | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | 
| 
| 
| 
| | Makes things a bit more modular.  As part of this process I also
replaced ct/x509 with crypto/x509, which already suits our needs. | 
| | |  | 
| | |  | 
| | 
| 
| 
| 
| | Added more documentation and quick helper scripts for now.  We need to
specify which signature schemes we expect/support from submitters. | 
| | |  | 
| | 
| 
| 
| 
| | Pretty much the bare minimum to load trust anchors from file and check
that the submitter's certificate chains back to something valid. | 
| | |  | 
|  | An STFE server instance that dials the Trillian gRPC back-end, and which
listens on six different HTTP endpoints but without any actual processing. |