| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
The major argument for moving input data from HTTP headers in GET
requests to body of POST's is that we define the protocol ourselves
without any dependencies on HTTP and can make it even simpler to
parse.
|
|
|
|
| |
Spotted by Rasmus.
|
|
|
|
| |
I think this is more markdownish.
|
|
|
|
| |
Mostly replacing "human-readable" with something more well defined.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This is the "header in, body out" idea written up. We might change to
a "POST body in, receive body out" scheme with "Content-Type:
application/stfe" if we can decide that POST is not a terrible idea
after all.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Specify who's verification key -- log, witness or submitter.
Move shard_hint and checksum in tree_leaf into its own struct, for a
more explicit definition of what to be signed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove all RSA support. Motivation: Simpler format for tree_leaf.
Replace percent-encoding with headers for indata and key/value in body
for outdata. Motivation: '<key>:<value>' is exactly what we want and
it works for output data (responses) and not only for input data
(requests).
Don't POST. Motivation: We don't need the complexity of POST since we
don't ever send a lot of data to the log.
Split up the get-signed-tree-head endpoint into three separate without
input data. Motivation: More explicit API plus easier debugging.
Change timestamps and shard hints to use seconds rather than
milliseconds. Motivation: time(1) and time(2).
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
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.
|
|
|