Bug#768577: systemd-cryptsetup handles keyfile differently from cryptsetup on plain mode

[intrigeri]

Hi Quentin,

Quentin Lefebvre wrote (17 Nov 2014 17:24:38 GMT) :
> I could provide a patch so that systemd-cryptsetup behaves the same way
> as cryptsetup.

> But actually, there is even an easier way to solve this: change the 'hash' parameter
> in /etc/crypttab to 'plain'.
> Doing this, cryptdisks_{start,stop} scripts work well, and so do systemd-cryptsetup
> (as it will pass a NULL pointer as hash parameter to cryptsetup, which is also legacy
> cryptsetup's way to handle keyfile + hash in plain mode).

Good to know, congrats for the debugging!

Now:

1. The proper solution still seems to patch systemd-cryptsetup so that
   this workaround isn't needed; may you please send your patch
   upstream? If not, just tell us and I guess someone here will do
   it :)

2. If a fix doesn't make it into systemd in Jessie, then I guess we'll
   want to document this workaround in NEWS.Debian, and make sure the
   release notes point there.

IMO, let's not spend time on #2 right now, and instead focus on #1.

Cheers,
-- 
intrigeri