Explore >> Select a destination
|
You are here 
|
blog.cryptographyengineering.com | ||
| | | | |
blog.trailofbits.com
|
|
| | | | | ||
| | | | |
blog.cr.yp.to
|
|
| | | | | ||
| | | | |
rot256.dev
|
|
| | | | | This is the companion post to a tool, git-ring, that I recently released on Github. Github/Gitlab makes the public keys of its users publicly available (at github.com/USERNAME.keys and gitlab.com/USERNAME.keys), this means that these services bind the users identity to public keys via this endpoint. Git-ring "exploits" this to enable the creation of (cryptographic) proofs showing membership among a set of users (or organizations) without revealing the identity of the person generating the proof. The publ... | |
| | | | |
keymaterial.net
|
|
| | | If you have been terminally online on IETF mailing lists, you might have seen this thread, where, in extremely uncharacteristic fashion for the IETF, everybody just agreed to only use the seed used in key generation for ML-KEM's private key instead of the format defined by NIST, something allowed by the NIST standard, but not... | ||
