Conversation

Replying to
I don't think we should be going after either of these people or blaming them for anything. It's a very clear misrepresentation of what I said. Please don't accuse me of something that I clearly didn't do. Thanks.
1
2
For simplicity, assume the CSPRNG for it is insecure. It could even be a totally insecure PRNG like XorShift. It could return zeroed values every single time. Does it matter, with how the standard proposes using it? I'll happily call it useless cargo cult nonsense, but backdoor?
Image
1
2
This is the same way the Linux kernel adds entropy from untrusted sources. An attacker can overwrite this data so the standard might as well be calling these fields attacker_input and extended_attacker_input. I don't understand why they even have the original non-extended one.
1
1
Show replies