| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
| |
If the provided tree size is (mostly) valid the Trillian back-end is
asked to provide an inclusion proof, which is then placed in an
InclusionProofV1 structure and returned as a JSON object.
|
|
|
|
|
| |
If the provided range is (mostly) valid the corresponding log entries
are fetched from the Trillian back-end and returned as a JSON object.
|
| |
|
|
|
|
|
| |
If the POSTed StItem can be parsed without errors it is handed over to
the Trillian back-end.
|
| |
|
| |
|
|
|
|
|
| |
An STFE server instance that dials the Trillian gRPC back-end, and which
listens on six different HTTP endpoints but without any actual processing.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
The metrics that one could derive can also be exported by the operator.
It is probably good enough and does not justify complexity right now.
|
| |
|
| |
|
|
|
|
|
|
| |
- Repurposed the CT/bis TransItem structure
- Added a "version 1 checksum" leaf
- Moved signature into leaf appendix
|
|
|
|
|
|
| |
- Added a basic Merkle tree leaf data structure that is extensible
- Added explicit references (where possible) to RFC 6962. More to come.
- Added TODOs that we need to think more about.
|
| |
|
|
|