Then please do not believe that blog post. Because /dev/urandom is not a
source of entropy and can not be relied upon for any serious business.
It is in a sense a consumer of entropy available from /dev/random, that
does an expansion to provide pseudo random data even when there is no
entropy to produce good random data.

@Jon Stevens:

Crypto should not be messed with. Period. But your frustration is
understandable. Developers do not intend to be hostile to novice users
as you claim, but we have concerns that not all users will not be able
to appreciate. rng-tools has a valid use case, but the workaround
suggested in some comments to use /dev/urandom would scare the crap out
of any cryptographer. I wish it is disallowed altogether.


The most sensible suggestion comes from Alvaro in #25. Why hasn't there been 
more discussion on this? Security can't be compromised, but a better 
explanation to users doees no harm. I am skeptic of allowing a flag, it will be 
suggested as a workaround when it should not be, and users will follow the 
advice.

Rather, only when being run interactively, the user can be prompted
after a timeout if they want to reduce the key size and/or proceed with
just the available entropy, since it is taking long to collect enough
entropy. This option should be unavailable when being run non-
interactively, since I don't see the need and IMO allowing it does more
damage in the long run.

On a sidenote, rng-tools should atleast spit out a warning when
/dev/urandom is being used as a *HARDWARE* random number generator,
which it is not. Does not prevent anyone from creating a new device node
for urandom and using it, and circulating sequence of commands to be run
to accomplish that, but all user stupidity can not be safeguarded
against.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/706011

Title:
  gpg --key-gen doesn't have enough entropy and rng-tools install/start
  fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/706011/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to