There is an entire javascript package dedicated to collecting entropy in that codebase. Hope that was well audited.pic.twitter.com/7xIhJapLrR
Voit lisätä twiitteihisi sijainnin, esimerkiksi kaupungin tai tarkemman paikan, verkosta ja kolmannen osapuolen sovellusten kautta. Halutessasi voit poistaa twiittisi sijaintihistorian myöhemmin. Lue lisää
Definitely want to make sure that clients using a browser that has been out of extended support for 5 years are generating secure random numbers too.pic.twitter.com/HZGx5PEzSQ
Ah....the reason there is so much new crypto code is because they lifted a ton of it from BouncyCastle and then changed things. Definitely a safe, maintainable approach.pic.twitter.com/X8xQ8PGmDI
Actually I take that back, there is some copying from BC, but it is definitely not the main reason for so much new crypto code. There appears to be some duplication too:https://twitter.com/analogist_net/status/1097591597678481408 …
Wow there are a couple of these kinds of comments....reassuring.https://twitter.com/malapropismus/status/1097602388993757185 …
When the prover and verifier share the same big warning message, which looks like it came from a review that was never followed up on...that's definitely not a good sign.pic.twitter.com/2xTjapcILe
I know the full audits were not released, but it is interesting to note that apparently some comments in the code point towards some of the earlier findings (& fixes).pic.twitter.com/QSM6gujkZv
this is the rare tweet that only gets better as you remove context...
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.