Three mistakes from Dart/Flutter's weak PRNG
1–10 of 93 posts
Re: Three mistakes from Dart/Flutter's weak PRNG
#2Re: Three mistakes from Dart/Flutter's weak PRNG
#3Re: Three mistakes from Dart/Flutter's weak PRNG
#4I’m not a Dart fan so maybe I’m biased, but wow this (from the article) is a failure on many levels: https://github.com/dart-lang/sdk/issues/56609
// TODO: Make this actually random
static int _initialSeed() => 0xCAFEBABEDEADBEEF;
Oops.Re: Three mistakes from Dart/Flutter's weak PRNG
#5[flagged]
Re: Three mistakes from Dart/Flutter's weak PRNG
#6[flagged]
I expect readers of HN to know the acronym PRNG, and that random must be seeded all the time and must NOT be used for secure things. But we're living in the age of LLMs that create perfect code while programmers know nothing anymore.
Re: Three mistakes from Dart/Flutter's weak PRNG
#7[flagged]
I expect readers of HN to know the acronym PRNG, and that random must be seeded all the time and must NOT be used for secure things. But we're living in the age of LLMs that create perfect code while programmers know nothing anymore.
Re: Three mistakes from Dart/Flutter's weak PRNG
#8[flagged]
The term is table stakes for the audience this is written for.
Re: Three mistakes from Dart/Flutter's weak PRNG
#9[flagged]
Why would you be reading this article if you do not?
This is the type of critique given when writing for a general audience, not a scientific whitepaper.
(Fun fact: The AP style guide tells folks to write at an 8th grade level because that's reading level of the average American adult. 8th graders do not read white papers on cryptographic design, and when they do, they look up unknown acronyms just like big boys and girls do.)