hi!
[email protected] 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 while the system
might be several thousand km away from you (or behind a locked door
or whatever), might do so, too, therefore i personally somehow don't
like an (unconditional) 'disabled' default.
apart from that, as i meant to indicate before, i got your point and
i wasn't really happy with the situation, too.
but i was wrong regarding my estimate of the effort necessary to
resolve this.
please see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=514213
for a solution (which can be applied without having to patch and
install resp. having to wait for a new package).
regards,
Chris
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
