Trusted URLs via Cryptographic Signatures
Edmond
28 points
13 comments
July 30, 2026
Related Discussions
Found 5 related stories in 738.6ms across 15,510 title embeddings via pgvector HNSW
- Don't Trust, Verify lwhsiao · 17 pts · March 28, 2026 · 57% similar
- You shouldn't trust Trusted Publishing woodruffw · 22 pts · July 07, 2026 · 53% similar
- TLS certificates for internal services done right mrl5 · 143 pts · July 09, 2026 · 53% similar
- Web-based cryptography is always snake oil enz · 108 pts · July 05, 2026 · 51% similar
- Trusted access for the next era of cyber defense surprisetalk · 72 pts · April 14, 2026 · 50% similar
Discussion Highlights (6 comments)
Edmond
SDK: https://github.com/CipherTrustee/certisfy-js Web of trust use case example: https://bsky.app/profile/bitlooter.bsky.social Experimenting with Keybase key holders as CAs: https://www.reddit.com/r/Keybase/comments/1q5ys71/using_keyb... Cryptographic Implementation of Exclusivity Agreements: https://github.com/CipherTrustee/certisfy-claim-recipes/tree... Build Your Own Trust Chain: https://blog.certisfy.com/2026/04/build-your-own-trust-chain... Some other examples of how you could leverage it: https://blog.certisfy.com/ Happy to answer questions.
mahemm
How does this differ from e.g. S3 pre-signed URLs?
westurner
How to implement signed URLs with W3C DID keys and W3C Verifiable Credentials?
Retr0id
What happens if the destination/contents of the URL changes after I sign it?
tgma
Google AMP had the concept of Signed Exchanges so that you can host content on a third party server while proving its integrity https://developer.chrome.com/blog/signed-exchanges Unfortunately, AMP itself was controversial and the system was not really adopted elsewhere, but it is something.
skinfaxi
What does this add over message signing?