@taligent "something wrong with the way entropy is captured for REMOTE sessions."
There's only a single way to generate entropy, and it's the same whether you're running gpg locally or remotely. It must come from an external source (eg keyboard/mouse/disk). Anything triggered by the machine itself is predictable due to the schedulers, it must come from user/disk activity instead. The only issue with generating it remotely is that it's harder to generate external entropy when you do not have physical access to the machine. Local keyboard/mouse input provides more noise than anything you can easily generate remotely. The find everything piped into cat trick in another session should be sufficient on most systems. If it is all cached this would allow you generate disk access bypassing the cache: dd if=/path/to/large/file of=/dev/null iflag=direct Personally I would suggest that you generate GPG keys *locally* where it's possible to generate plenty of entropy since you have keyboard/mouse access, then transfer the keys to the remote server(s) where it's required. Yes, perhaps the message could be improved with advice targeted at remote users and a progress indicator if the kernel allows it, but that does not describe the original poster's report and might be better with this bug closed and that suggestion raised as a separate bug. Otherwise it may be dangerous for people Googling this issue to find this bug and follow the original posters advice without reading any further. -- 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
