Incidentally: Noise is great, but it's also fine to use TLS, if you're just a little careful.
See also:
Incidentally: Noise is great, but it's also fine to use TLS, if you're just a little careful.
See also:
http://www.daemonology.net/blog/2009-06-11-cryptographic-rig...
Blanket "don't use X" statements are much more useful with context and information about why not to use X (and when using X may be required, useful, or a better choice).
https://sockpuppet.org/blog/2014/02/25/safely-generate-rando...
Just because the article recommends seeding over using /dev/random early at boot time doesn't mean the original gist shouldn't mention these issues so that readers are aware of them.
Just saying "use /dev/urandom all the time" without mentioning the caveats we're discussing here means someone might read your article and in a (misguided) appeal to authority implement something solely on your recommendation without doing their research properly first.
I would have thought someone writing security articles would want to avoid misleading someone into implementing something that's accidentally insecure. I hope I'm not wrong.
http://www.2uo.de/myths-about-urandom/
And another:
http://security.stackexchange.com/questions/3936/is-a-rand-f...
Which backs up my point that using /dev/urandom blindly without knowing about some of the edge cases isn't a good idea, and lists those edge cases and what to do about them (which is what I suggested you do too).
> And another: > http://security.stackexchange.com/questions/3936/is-a-rand-f....
Which also lists the edge cases I'm talking about.
Hey look if you just want to say "I'm aware of the edge cases and don't want to put them in my gist for others to see" that's fine with me, but dodging the issue by claiming there are no edge cases (and then listing 3 articles which all mention the edge cases) isn't the right reply I think.
Don't be surprised if someone suggests that a gist listing security best practices list some edge cases that go along with the blind advice too. Feel free to disagree, but at least disagree honestly.
Why not be complete and list the caveat, instead of incomplete and possibly lead that one in a thousand down the wrong path?
And lots of articles about best practice leave out very rare edge cases. No advice is always always right.
I don't think that's an argument in support of leaving out edge cases, and even if you disagree in general, I think security articles should be more diligent than random best-practices articles.
> Far more than one in a thousand will use it as an excuse to do the wrong thing.
If an article says "always do X" and someone does X and the implementation is subtly wrong or insecure, that's an argument to improve the article (which is what I'm suggesting).
But if an article says "almost always do X, and be aware of this edge case" and someone gets it wrong by not following instructions, then I don't think the article is at fault.
I would personally want my security advice to cover any edge case I could think of, even if only in the footnotes.