Explore >> Select a destination
|
You are here 
|
soatok.blog | ||
| | | | |
scottarc.blog
|
|
| | | | | This isn't (necessarily) a security vulnerability; merely an observation that I don't think has been articulated adequately within the cryptography community. I thought it would be worth capturing somewhere public so that others can benefit from a small insight when designing cryptosystems. Background Once upon a time, there was Symmetric Encryption, which provided confidentiality, but... | |
| | | | |
paragonie.com
|
|
| | | | | A developer's short guide to encryption, authentication, and authenticated encryption with examples in PHP | |
| | | | |
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... | |
| | | | |
electric-sql.com
|
|
| | | Local AI with Postgres, pgvector and llama2, running inside a Tauri app with realtime sync powered by ElectricSQL ?? This is the architecture of the future! | ||
