Bug#524728: [mar...@better.se: Bug#524728: dropbear: cryptroot boot broken by dropbear remote unlocking feature]

2009-04-29 Thread Gerrit Pape
. - Forwarded message from Marcus Better mar...@better.se - Subject: Bug#524728: dropbear: cryptroot boot broken by dropbear remote unlocking feature Reply-To: Marcus Better mar...@better.se, 524...@bugs.debian.org Date: Sun, 19 Apr 2009 20:27:09 +0200 From: Marcus Better mar...@better.se User-Agent

Bug#524728: [mar...@better.se: Bug#524728: dropbear: cryptroot boot broken by dropbear remote unlocking feature]

2009-04-29 Thread debian
hi! and instead of the usual cryptsetup password prompt, it prints a message about starting dropbear and then stuck. I should add that it printed IP-Config: eth0 ... and apparently tried to configure eth0 with DHCP, but that interface is not connected to any network. (Perhaps that would

Bug#524728: [mar...@better.se: Bug#524728: dropbear: cryptroot boot broken by dropbear remote unlocking feature]

2009-04-29 Thread Marcus Better
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 deb...@x.ray.net skrev: when your initramdisk is built, you should get the following warning: I somehow missed that. Anyway IMHO it's not enough with a warning for a change that is almost guaranteed to render a system unbootable. It should just be

Bug#524728: [mar...@better.se: Bug#524728: dropbear: cryptroot boot broken by dropbear remote unlocking feature]

2009-04-29 Thread debian
hi! deb...@x.ray.net skrev: heh, so i kind of skreved up or what? ;) I somehow missed that. Anyway IMHO it's not enough with a warning for a change that is almost guaranteed to render a system unbootable. It should just be off by default. not having a way to unlock a cryptroot from remote