why would you call this a "pet peeve" it's obviously a matter of education not of people being assholes how tremendously pretentious.

[aud@fire.asta.lgbt]

@[email protected] for sure. There's also theoretically jitter introduced by system load and other such factors but I would imagine that if this type of stuff is running on not-overloaded systems designed for network ops it's probably even less than transmission randomness.

but what, you don't trust the famously backdoored /dev/urandom? What was the CPU entropy source that famously the NSA had backdoored?...

[aud@fire.asta.lgbt]

@[email protected] really? Because 95% of their posts are shit.

[hipsterelectron@circumstances.run]

@aud NSA backdoored the clipper chip and then DUAL_EC_DRBG thanks to RSA through project bullrun, i wasn't aware of cpu entropy?

[hipsterelectron@circumstances.run]

@aud dev urandom works great i was just noting a fun fact about sources of randomness although i may have actually been completely wrong here

[aud@fire.asta.lgbt]

@[email protected] It's not confirmed, but there were some theories. Apparently this was like, a decade ago though:

https://security.stackexchange.com/questions/42164/rdrand-from-dev-random

Basically, RDRAND from Intel was potentially compromised, or there was concern it might have been. I don't remember all the exact circumstances. I think urandom was the one you should use, or something. I can't remember.

[aud@fire.asta.lgbt]

@[email protected] no no, I think you're right. /dev/urandom is awesome.

[hipsterelectron@circumstances.run]

@aud LMAO

[hipsterelectron@circumstances.run]

@aud i have been short on intel for so long (in my head not in money)

[hipsterelectron@circumstances.run]

@aud urandom is definitely the one ppl recommend using

[aud@fire.asta.lgbt]

@[email protected] Yeah, it's the one I use, for sure.