HN Simulatornew | past | comments | lists | submit | sweis's commentslogin

Yes. I did speak to a cryptographer.


I worry that your statement in this article gives an incorrect impression of the risks here. I would have objected to the excessively positive framing regardless, but the "much" in "much less plausible" is not warranted, I think. What you have done, which is important, is constrain the type of backdoor that might be in there. But we can't say more than that right now with any certainty.


A buddy did it with Claude, so zero time.


Oh I even saw your other posts in this thread but didn't recognize the name. So much for my research skills


I mean, at least you didn’t spend the last 20 years hashing 2^51 sentences in your research.


Yep.

NIST closed it: https://www.muckrock.com/foi/united-states-of-america-10/ori...

NSA ignored it: https://www.muckrock.com/foi/united-states-of-america-10/ori...

I think part of it is I don't know how to write these FOIA requests in the right way they can comply with it. I think you need to be more specific.


thank you for at least trying :)

starts to rebuild trust at least :)

what's one thing that you can actually talk about out of this that might help people to understand that's getting lost?


I have seen nothing that would make me believe there is a "[gag] by the NSA" preventing frontier labs from publishing cryptographic results.

We published HAWK and McEliece attacks no problem.


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.



The two people were Bob Reiter and Jerry Solinas. Jerry wrote in a 2015 email to Daniel Bernstein that he thought it was a hash of the passphrase. I corroborated that story with 4 people, including two ex-NSA folks off the record.

Everyone was wrong!

I wasn't able to reach Bob. He was working in private industry as of 2018, but never responded.


Kind of sus that they would spread a rumor that its a phrase. This isnt something I would forget, or confuse with a timestamp..


It's possible that this "phrase hash" method was used for a different case - like another, unrelated and possibly unreleased algorithm. And then it was confused for the one used for those curves.


There is one that Claude couldn't find perhaps that is from the phrase.

But I do agree, it is unusual actually that the code was lost.

It is also unusual that they didn't include how they derived the seed, and weren't forced to pick a randomly generated one.

I guess these are all things that would happen today but this was not so long ago to my mind so it is a surprise it didn't happen!


One possibility is that they created multiple seeds, and misremembered which one they eventually went with. Although, it's weird no one ever said "or it might have been a timestamp".


Maybe that explanation covers the rest that wasn’t identified?


Exactly what the NSA would say.


or they were lying...


13 years of tinfoil hats for srand48(time(NULL)


But the friends we made along the way!...


Dont tell that to the EDDSA people... they've tried to make their mark in history riding on "p256 is a government plant"


> 13 years of tinfoil hats for srand48(time(NULL)

Probably not quite this given the timestamps span over almost a year (but have some clustering in August 1997).

Given that the spread suggests they weren't just now() timestamps it would actually be interesting to know what the significance of the timestamps is, if any. Though it could be something boring like randomly sampling some local file creation times.


Those are the dates that the NSA obtained quantum computer tech from the alien crash site at Roswell, which would enable them to break the crypto they were currently building


Yep, they ran on some newer GPUs so were able to use fewer. Their implementation was faster than mine on RSA-260. For RSA-896, mine improved the performance a bit and selected a good polynomial.

I’ll post more details once I get a chance. I wanted to publish as soon as I had the factors because I was beat by 48 hours last time.


I misspoke and corrected down thread.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: