The article says it goes from only blocking on boot until it has sufficient entropy, to never blocking.
-
-
-
Blocking until the pool has initialised and then never again is the correct behaviour. (I think that should be an uncontroversial statement but see retweeted article for reasons.) However, never blocking would be bad because it causes issues like http://smartfacts.cr.yp.to/smartfacts-20130916.pdf …
- Još 1 odgovor
Novi razgovor -
-
-
Maybe related to this? https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=72dbcf72156641fde4d8ea401e977341bfd35a05 … See also https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.3-Released … ... not sure if related.
-
Thanks. That seems to suggest that it didn't happen, at least in 5.3, because Linus reverted a change that improved ext4 instead?
- Još 1 odgovor
Novi razgovor -
-
-
Pretty sure the article is wrong. Although Linus was talking about making getrandom nonblocking, he ultimately went with this commit instead:
- Kraj razgovora
Novi razgovor -
-
-
It was discussed on /r/crypto herehttps://www.reddit.com/r/crypto/comments/djp4yn …
Kraj razgovora
-
-
-
to the best of my knowledge this is BS and not using getrandom wrong. it's the best interface for cryptographically secure (pseudo) random numbers we have on this platform today.
-
Once Ted Tso retires, I guess we can fix it. Stephan Mueller wrote the code already

- Još 1 odgovor
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.