Remix.run Logo
▲ tptacek 3 hours ago

This is devastating news... for an entire generation of NIST cryptography conspiracy theories.

▲nickysielicki 2 hours ago | parent [-]

It’s perplexing that NIST chose to burn so much trust and goodwill with the independent cryptography community instead of just explaining empirically that they really had nothing up their sleeve.

▲sweis 2 hours ago | parent | next [-]

I think they legitimately did not know. The person who worked on it directly, Jerry Solinas, did not remember and gave an explanation that turned out to be wrong. In his defense, multiple people told the same story about hashing a phrase that was wrong.

If they did know, they could have handed over these timestamps 15 years ago and put the issue to bed.

▲tptacek 2 hours ago | parent | prev | next [-]

It was a very different time back then.

▲thoughtpeddler 14 minutes ago | parent [-]

What was so different, culturally?

▲SturgeonsLaw 2 minutes ago | parent [-]

Well the thing that comes to mind for me was the US gov classing encryption as a munition and placing it under export controls

▲yrjrjjrjjtjjr 2 hours ago | parent | prev | next [-]

If they deny everything they didn't do, then whatever they don't deny will stand out.

▲rs_rs_rs_rs_rs 2 hours ago | parent | prev [-]

"independent cryptography community" - I actually LOLed at this

I don't think that "community" would accept any kind of answer as truthful so why waste the time...

▲nickysielicki 2 hours ago | parent [-]

It’s independently verifiable. What do you mean?

▲valleyer an hour ago | parent [-]

One of the top comments in this very thread suggests the seed timestamps were maybe selected specifically for purpose.