Proofable VS trillian

Proofable

We haven't tracked posts mentioning Proofable yet.
Tracking mentions began in Dec 2020.

trillian

• Is there a good example of an open source non-trivial (DB connection, authentication, authorization, data validation, tests, etc...) Go API?
  14 projects | /r/golang | 25 Jan 2023
• Key transparency: A transparent and secure way to look up public keys
  3 projects | news.ycombinator.com | 26 May 2022

  Archived. Not sure when. :( I'm not sure what if anything is a decent replacement/substitute.

  In the README examples I see text about what I think is Certificate Transparency. That was definitely the first thing this made me think of. There's also a lot of talk in the project about CONIKS[1], & associate research papers are about 'bringing key transparency to end users'.

  The scenarios[2] are interesting, but I'm not sure fully how this project helps. They explicitly call out Upspin for encrypted storage, which was linked recently[3].

  It appears to make heavy use of the Trillian cryptographically verifiable data store[4].

  [1] https://www.schneier.com/blog/archives/2016/04/coniks.html

  [2] https://github.com/google/keytransparency/blob/master/docs/s...

  [3] https://news.ycombinator.com/item?id=31520559

  [4] https://github.com/google/trillian

• GnuPG used to ask for your support to help protect online privacy
  8 projects | news.ycombinator.com | 28 Dec 2021
• Threat Actors Now Target Docker via Container Escape Features
  5 projects | news.ycombinator.com | 13 Feb 2021

  https://stackoverflow.com/questions/37058322/how-can-i-verif...

  CT (Certificate Transparency) is another approach to validating certs wherein x.509 cert logs are written to a consistent, available blockchain (or in e.g. google/trillian, a centralized db where one party has root and backup responsibilities also with Merkle hashes for verifying data integrity). https://certificate.transparency.dev/ https://github.com/google/trillian

  Does docker ever make the docker socket available over the network, over an un-firewalled port by default?

• Tamper-Evident Logs
  3 projects | news.ycombinator.com | 1 Feb 2021

  - another can verify the accuracy/validity/goodness of things in the log (e.g. in CT it's the domain owner who is in the unique position of saying "yes, I asked for this cert to be created", for binaries it might be "I'm the authorised creator of these binaries and, yup, that was me" or "I'm a respectable malware scanning company, and this binary doesn't match any known signatures", "I'm an auditor and these transactions are complete and correct", etc. - you can probably think of many more examples!)

  In this light, you can think of a tamper-evident log as being a sort of "reliable transport" to connect these different types of clients together, and importantly, where they all can prove to each other (using those light weight tree heads + consistency/inclusion proofs) that they're seeing the same set of data in the log - or, if they can't prove it - they have the cryptographic evidence of operator of the log operator having done something unexpected.

  If you have a spare few mins, have a look at the Claimant Model docs here: https://github.com/google/trillian/tree/master/docs/claimant...

  3 projects | news.ycombinator.com | 1 Feb 2021

  Yeah, right on!

  We're looking in more depth at other use cases, developing a better understanding of which types of problems this might be useful for, and ways to reason about the properties you want/get from using systems like this (e.g. https://github.com/google/trillian/tree/master/docs/claimant...)

  [Disclaimer: I work on CT, Trillian, and some other related projects]