-
-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Attestation transparency logs #13
Comments
I had a (rather "ambitious") idea of how this could be done using BFT consensus around quorum builds: https://github.com/iqlusioninc/synchronicity/blob/develop/README.md#about A simpler approach would be to log to something like Google Trillian. |
I'd love to explore the possibility of using BFT. I think the question regarding trillian would be to create a profile, which is something we've explored of doing in the in-toto team... |
Trillian "Personality", but yes https://github.com/google/trillian/blob/master/docs/Personalities.md The Golang "SumDB" uses one for this purpose, I believe: https://go.googlesource.com/proposal/+/master/design/25530-sumdb.md |
I personally have some motivation to look into the sumdb code from golang. It's frankly simpler then the trillian monstrosity using grpc and god knows what. |
@Foxboron sumdb uses Trillian: https://blog.golang.org/module-mirror-launch
|
Wait, what. Now I'm confused by what the mod/sumdb is suppose to contain. There is no traces of trillian anywhere in their github org. Is the backend proprietary? |
It contains a client for verifying https://go.googlesource.com/proposal/+/master/design/25530-sumdb.md#checksum-database The verifiable log behind https://sum.golang.org is managed by Trillian. I'm not sure if the personality they're using is open source or not (I can't find it quickly, but have pinged the relevant people) |
Right, so I checked the gopher slack and it is indeed proprietary. It's apparently "not a lot of code" on top of trillian, but the storage code is heavily tied to what I assume is GCP and the storage there. That is a bit unfortunate I think. |
In extension to #12 there should be a tamper resistant log, similar to certificate transparency.
The text was updated successfully, but these errors were encountered: