datly VS trillian

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

Related is Google Trillian: https://github.com/google/trillian

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?

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]