simple-jwt-provider
Key Transparency
| simple-jwt-provider | Key Transparency | |
|---|---|---|
| - | 4 | |
| 38 | 1,557 | |
| - | - | |
| 0.0 | 1.0 | |
| about 1 year ago | almost 3 years ago | |
| Go | Go | |
| MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
simple-jwt-provider
We haven't tracked posts mentioning simple-jwt-provider yet.
Tracking mentions began in Dec 2020.
Key Transparency
-
DTLS-SRTP spoofing
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.
-
Key transparency: A transparent and secure way to look up public keys
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
-
Why Doesn't Email Use Certificates?
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.
What are some alternatives?
go-proxy-cache - Simple Reverse Proxy with Caching, written in Go, using Redis.
Vault - A tool for secrets management, encryption as a service, and privileged access management
minio - The Object Store for AI Data Infrastructure
SFTPGo - Fully featured and highly configurable SFTP server with optional HTTP/S, FTP/S and WebDAV support - S3, Google Cloud Storage, Azure Blob
Caddy - Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS
RoadRunner - 🤯 High-performance PHP application server, process manager written in Go and powered with plugins
traefik - The Cloud Native Application Proxy
etcd - Distributed reliable key-value store for the most critical data of a distributed system