Dude... Come on - why does everything have to be a ridiculous tug of war?
> getrandom(...,0) isn't the blocking version of getrandom
As I have pointed out, and Cory pointed out in that thread - getrandom(flags=0) does block in the rare occasion that blocking is needed and at no subsequent time. That's all I said.
> nor is it equivalent to /dev/random
When did I say that is was? When did I ever even mention /dev/random?
You are the only one that keeps bringing up /dev/random. Instead of refactoring my statements and then taking a nugget of knowledge in an effort to disagree with me and win a point: read what I have actually written. Please. Just slow down a little.
I really don't want to argue with you any more. I do hope that you stop hammering the "use urandom use urandom use urandom waaaahh" thing, but I can't control you.
The right answer moving forward, for almost everyone, is getrandom, not urandom.
The truth is: before I opened that stackexchange question, I was only 90% sure. But now I'm confident I have the right answer. If I'm still wrong, then by all means correct me - you have a link to the open stackexchange question.
Python has done the right thing. So have other toolchains. As far as I can tell, everything is good. We can all just chill.
The "right" behavior you're referring to was literally motivated by the article you're criticizing as "dangerous", as is, I believe, the default behavior of the system call itself.
> getrandom(...,0) isn't the blocking version of getrandom
As I have pointed out, and Cory pointed out in that thread - getrandom(flags=0) does block in the rare occasion that blocking is needed and at no subsequent time. That's all I said.
> nor is it equivalent to /dev/random
When did I say that is was? When did I ever even mention /dev/random?
You are the only one that keeps bringing up /dev/random. Instead of refactoring my statements and then taking a nugget of knowledge in an effort to disagree with me and win a point: read what I have actually written. Please. Just slow down a little.
I really don't want to argue with you any more. I do hope that you stop hammering the "use urandom use urandom use urandom waaaahh" thing, but I can't control you.
The right answer moving forward, for almost everyone, is getrandom, not urandom.
The truth is: before I opened that stackexchange question, I was only 90% sure. But now I'm confident I have the right answer. If I'm still wrong, then by all means correct me - you have a link to the open stackexchange question.
Python has done the right thing. So have other toolchains. As far as I can tell, everything is good. We can all just chill.