RFC: initialize /dev/urandom, is it necessary? Can we do it in a better way?
Roberto A. Foglietta
roberto.foglietta at gmail.com
Mon Jan 26 14:04:19 UTC 2026
On Tue, 19 Sept 2023 at 09:10, Guillermo Rodriguez Garcia
<guille.rodriguez at gmail.com> wrote:
>
> El martes, 19 de septiembre de 2023, Roberto A. Foglietta <roberto.foglietta at gmail.com> escribió:
>>
>> Guillermo confused the information with the entropy.
>>
> I didn’t confuse anything. Please leave me out of your arguments, thank you.
>>
>> Guillermo is getting mad and screaming
>>
>
> :-?
> You definitely need help.
>
For sure I need help, but not the kind you had imagined in 2023.
Anyway: it does not exist "collectible entropy", just structured
information. Because once "entropy" has been collected becomes data
not entropy. Sometimes that structure does not exist because is
white-noise random.
Grok defined this kind of "behaviour" as typical of usenet trolling:
when people create theoretical problems by trick definitions or
precision expectancy which are not context related or fact based. I
don't trust Grok, I trust that machine can collect and reveal precious
information by talking about quak machines or whatever else.
Considering that Grok is the AI adopted by the US military (and
Pentagon) you might have just a glimpse of HOW much it can reveal
under certain circumstances.
Physics still wonders what entropy is and here somebody pretends to
collect it. Let me be clear, there are just "smart" or "dumb" ways of
messing bits, and nothing else. However, this is not just "steryl" and
"polemic" years-after answer. Military security is strongly related to
this stuff, which is probably the reason why so many people (even
experts) are so much confused about the fundamentals (because you have
been convicted of absurdities, you act coherently but heractly -- also
known as who can let people trust absurdities can push them to commit
atrocities). Here we are: yes I need help, but among us, you all
apparently are in need of much more.
~> https://github.com/robang74/working-in-progress/blob/main/random.txt
If a process like the one described here is operated by the CPU
microcode, it would be safely bound by the CPU itself, a modern CPUs
can be seen as very good random generators because of their jitter
unpredictability in executing tasks.
How good is this kind of random generator based on CPU arch and
microcode to be good at providing unbreakable cryptography assuming
the whole process is made at
the state of art? Who design the chip (or made the chip) and deliver
the microcode can definitely have access to every ciphered
communications no matter what.
(Good morning and yes, I am the guy who is claiming "that" money:
https://github.com/sponsors/robang74)
Best regards,
--
Roberto A. Foglietta
FGLRRT74C26D969F
+49.176.274.75.661
+39.349.33.30.697
More information about the busybox
mailing list