POST
- Total posts
- 605
- Total predictions
- 1
- Success rate
- 0.0%
- Avg score
- 0.00
POST
POST
Terminating/padding each absorbed chunk in Keccak/SHA3.
I'm deriving the session keys using Keccak/SHA3 by absorbing three(3) things: (1) the salt, (2) the common secret and (3) bits from a common key file. Normally, all three are concatenated and then padded, and the whole thing is absorbed. …
POST
A Different 'H' in Ed25519
I understand that the Ed25519 variety of EdDSA uses SHA-512 for the random oracle H. Would replacing H with Keccak be provably secure? I'm in a situation where the systems are constrained in ROM and RAM. Using Keccak in Ed25519 …
POST
POST
POST
How is SHA3 (Keccak) Considered More Secure Than SHA2.
Hello, I was wondering why SHA3 is considered more secure than SHA2. I also was wondering about Shake256 vs SHA3 as I’m implementing SLH-DSA for my application. Thanks.
POST
Where can i discuss my cryptography-heavy vibecoded project?
cryptography and vibecoding is not a combination thats appealing to many. my code and my documentation dont seems to be to the "quality" as expected. so recently i post my project on vibecoding subs. its well recieved there, but i …
POST
POST
otrv4+ v10.6.13 is up. Identity keys fully Rust-owned now, plus a quick SMP bug fix.
Shipped v10.6.12 and v10.6.13 together because the first one broke something. The main change is that long-term identity private keys now live inside Rust SecretBytes with ZeroizeOnDrop. Python only sees public bytes through the handle API, never the raw private …