Open phbnf opened 4 days ago
A few weeks ago, I wrote two experiment PRs, that handled i, ii, iii, iv and v.
Changes for i, ii, iii, and iv are not that big, but may require further rearchitecturing shall we decide for the hammer tool to optionally supports CT with flags for instance.
I did something a bit special for v. that I think is out of scope of this issue (though it might be a nice-to-have): instead of generating chains locally, it plugged the certificate-transparency-go/.../scanlog tool into trillian-tessera/.../hammer. Since a lot of things have changed on the hammer since I wrote this, and especially that would impact point v. with respect to deduplication, I think that it won't work anymore. But I'll give it a go when I come around to it. For history and inspiration, here are the two PRs that resulted from this, which I have rebased on main/master.
We need to both have a conformance and load test for the SCTFE binary.
Today, we have:
add-chain
andadd-pre-chain
requests, which work with the SCTFE with no modification. However, the read paths are not compatible, so it does not work as a conformance tool.add
endpoints:add-chain
andadd-prechain
instead/tile/data
instead of/tile/entries
TileLeaf
, and instead of sequences ofbig-endian uint16 length-prefixed
entries