Re: dropbear delayed startup

2013-02-12 Thread Mike Mestnik
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/12/13 15:11, Lukas Schwaighofer wrote: > Hello Mike, > > thanks for your answer. > > On 12.02.2013 21:05, Mike Mestnik wrote: >> What issue do you have, sounds like you are just generally >> concerned. You should direct concerns to the authors

Re: dropbear delayed startup

2013-02-12 Thread Lukas Schwaighofer
Hello Mike, thanks for your answer. On 12.02.2013 21:05, Mike Mestnik wrote: > cryptsetup does not encrypted filesystems, so you must be mistaken > if you believe that you are "remote unlocking of encrypted > filesystems" with cryptsetup. Be specific about your configuration, > this is importa

Re: dropbear delayed startup

2013-02-12 Thread Mike Mestnik
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lukas, cryptsetup does not encrypted filesystems, so you must be mistaken if you believe that you are "remote unlocking of encrypted filesystems" with cryptsetup. Be specific about your configuration, this is important in this case. Those looking f

dropbear delayed startup

2013-02-12 Thread Lukas Schwaighofer
Hi, I started using remote unlocking of encrypted filesystems within the initramdisk (as provided by the cryptsetup/dropbear packets) some time ago. However I am worried because of the potentially low entropy during the execution of the initramfs and dropbear using /dev/urandom as a source for ran