24 ms·
The programs in question were not manually seeding the RNG, as was patio11's suggestion. The app implementors in this case don't seem to have actually done anyt
by glurgh 13y ago
The programs in question were not manually seeding the RNG, as was patio11's suggestion. The app implementors in this case don't seem to have actually done anything wrong at all.
- marshray 13y agoBut it took us days to arrive at this conclusion.
- j_s 13y agoI believe this is the point in the discussion where people willing to do some digging indicated that the problem was most likely not in the apps: https://news.ycombinator.com/item?id=6195707 https://news.ycombinator.com/item?id=6195707 It wasn't days, but I can't say for sure that it was minutes... my vote would be for hours! :)
- glurgh 13y agoOnce it was clear what library was in use (on the day of the original announcement) it literally took minutes to eliminate that particular one. You're right that it's taken days to learn what the precise problem is - but that's exactly why I'm saying prematurely assigning blame is a mistake!
- tptacek 13y agoIt really did take minutes to see that the bug was almost definitely not bitcoinj or the SpongyCastle code explicitly seeding the CSPRNG with crap.