cryptsetup should have a smarter initramfs conf-hook so ubuntu-desktop can include it by default

DK-Disks currently suggests cryptsetup, which is the right relation wrt. the devicekit-disks package itself.

The real question is whether we want to add this to ubuntu-desktop. From my side I'd love to, since it's very useful to have for USB sticks and the like.

Scott, is there anything which we need to fix in cryptsetup before making it acceptable for installing by default? (In terms of slowing down boot, plymouth integration, and the like).

On Wed, 2009-12-23 at 14:37 +0000, Martin Pitt wrote:

> Scott, is there anything which we need to fix in cryptsetup before
> making it acceptable for installing by default? (In terms of slowing
> down boot, plymouth integration, and the like).
>
It must not have any initramfs script, init script or upstart job that
is run in the default case (which isn't true right now).

Having udev rules or upstart jobs only fired as a result of events
signifying the presence of a disk it can handle is fine.

Note that I don't consider having an initramfs script, init script or
upstart job that uses "test" to decide whether to run fine. These cost
a surprisingly significant amount of time, and we don't need them for
things like RAID and LVM.

Also iirc, cryptsetup right now, when installed, forces a framebuffer
and splash screen into the initramfs (so it can ask for a root disk
password); obviously that's incompatible with being installed by
default.

(It's also probably worth noting that cryptsetup is one of those things
that exists on the LiveCD and is removed from the system by ubiquity
when not needed - which makes it more special.)

Scott
--
Scott James Remnant
<email address hidden>

Another option would be to splitout a cryptsetup-bin which ships the binary only, which is enough for USB devices. Then we can seed this, and leave handling of the full cryptsetup package to ubiquity/d-i as done now.

On Wed, 2009-12-23 at 16:04 +0000, Martin Pitt wrote:

> Another option would be to splitout a cryptsetup-bin which ships the
> binary only, which is enough for USB devices. Then we can seed this, and
> leave handling of the full cryptsetup package to ubiquity/d-i as done
> now.
>
Yup;

another would be having a cryptsetup conf-hooks.d figure out whether
it's needed in the initramfs, and if so set CRYPTSETUP=y and
FRAMEBUFFER=y - then have OPTION=CRYPTSETUP in the cryptsetup script

(Though the init script would have to go)

Scott
--
Scott James Remnant
<email address hidden>

There's no longer an init script that's run on startup, but there is an upstart job that's 'start on stopped udevtrigger' which we don't have a good way to get rid of (...short of making the other upstart job run on *all* disks, not just those that are ID_FS_USAGE=crypto). I guess a package split would be necessary.

The package has been split as of precise, cryptsetup support is now included in ubuntu-desktop.