Trickster VS Key Transparency

Are you thinking of something like nginx which would drop the cache periodically? Which would do this: https://github.com/trickstercache/trickster but for any http request?

However, a MITM controlling the signaling server could manipulate any attempt to communicate the fingerprint between the endpoints. Hence why certificate verification should be out-of-band (with regards to the signaling server). The most common solution I've seen is that the call participants can just read the fingerprints to each other and ensure they match. But there are other solutions including using a trusted third party, or even key transparency... because blockchain.

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

Key Transparency is an example of such a system, built on a highly scalable backend system (Trillian, which powers Certificate Transparency), but it's been under development for several years without a production deployment.