If someone has replaced your `/dev/random` with `/dev/zero`, you have already lost and there is nothing you can or should reasonably do besides nuke the machine from orbit. Here are some of the things you can now do with Streak + Zapier: Create a Streak box every time someone fills out a Wufoo form Create a Streak box every time a new Gmail message comes in matching a certain criteria (i.e. The rest go into situations that - quite frankly - border on ludicrous. And even then, using a library like the one the GP is using doesn't actually help, since it's virtually guaranteed to just be reading bytes from `/dev/urandom` for its seed in the first place. Anyone who is writing code for these environments is almost certainly already aware of these limitations. This is, quite simply, not a concern for anyone not writing code for specific embedded devices or for extremely early in the kernel boot process. His second argument is that /dev/urandom might not have enough randomness in it. His "improved" code is simply an optimization around retrying from this device, but it's not an improvement in safety. And even if it were, the author's original code (and my description of an implementation) already works! The `read` call will return an error, and that error is handled. I am unaware of any system where this is actually possible.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |