cryptsetup does not support the 'keyscript' crypttab option when used with systemd

Bug #1642955 reported by Yuri W
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cryptsetup (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Our company is using Ubuntu as our main OS now. Before we decided to switch to 16.04 (with systemd) we used keyscript= crypttab option to manage some of our encrypted volumes.
Now with Systemd that's no longer possible and we're forced to use upstart, which in itself contains several nasty bugs at this time (these aren't exactly the scope of this bug though).

Due to removed functionality that was present in previous release, I still consider this a bug in cryptsetup even though it's related to upstream. I know that systemd introduced a concept of 'password agents' but AFAIK there's no way to automate the process of getting block device keys - because these agents only accept ASCII text (and our keys are already binary, that'd take a huge effort to redo everything to use, say, base64 anyway).

Revision history for this message
Yuri W (wildylion) wrote :

wrong package chosen

affects: upstart (Ubuntu) → cryptsetup (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in cryptsetup (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.