As I said above, I may have been to overenthusiastic closing this bug, and I apologize for that, but there is no need to accuse me of knowing little of encryption. Please don't get personal and keep this here on a professional level.
/dev/random and /dev/urandom are both random number generators, but /dev/urandom is only a _pseudo_ random number generator, its generated output is still hard to predict. If you are paranoid (and I can understand that, because I'm paranoid sometimes, too), then /dev/urandom is not secure enough for you, but for other people it may be sufficient. Since /dev/random/ can run out of usable entropy, it is not a bug, but expected behavior that you have to press keys or move the mouse or whatsoever to generate new random numbers, which will speed up the boot process. When encrypting the swap partition, /dev/urandom can be used to generate a random key file, so you still had to reconstruct the exact sequence that was generated at the moment of initializing the encrypted swap partition, which is very, very hard. Some links about this topic: https://help.ubuntu.com/community/EncryptedFilesystemHowto5 https://www.antagonism.org/privacy/encrypted-swap-linux.shtml Buttom line: I fully agree with you that using /dev/urandom raises security questions. As you can see, both tutorials prefer /dev/random, but they also states that this might require you to press some keys, which strengthens my positions that this is NOT a bug. Btw: I found an earlier bug report and I think, this one here is a duplicate of Bug #223072 -- [jaunty] encrypted swap breaks (or slows a lot) the boot https://bugs.launchpad.net/bugs/367260 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
