On Sun, Apr 20, 2014 at 09:55:11PM +0300, Mantas Mikulėnas wrote:
On 2014-04-20 21:45, Matthew Monaco wrote:
And of course, the third option would be to submit a patch. The
src/cryptsetup
stuff is pretty straightforward.
Wasn't one submitted just a month ago?
Yes, patches 1/3 and 2/3 were
On Sat, 19.04.14 13:49, Nikolaus Rath (nikol...@rath.org) wrote:
Hello,
I have several LUKS encrypted volumes that use the same
passphrase. Before switching to systemd, I have used the decrypt_keyctl
keyscript to cache the passphrase, so that I have to enter it only once.
As far as I can
On 04/19/2014 02:49 PM, Nikolaus Rath wrote:
Hello,
I have several LUKS encrypted volumes that use the same
passphrase. Before switching to systemd, I have used the decrypt_keyctl
keyscript to cache the passphrase, so that I have to enter it only once.
As far as I can tell, the systemd
On 2014-04-20 21:45, Matthew Monaco wrote:
And of course, the third option would be to submit a patch. The src/cryptsetup
stuff is pretty straightforward.
Wasn't one submitted just a month ago?
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel
Matthew Monaco m...@monaco.cx writes:
On 04/19/2014 02:49 PM, Nikolaus Rath wrote:
I have several LUKS encrypted volumes that use the same
passphrase. Before switching to systemd, I have used the decrypt_keyctl
keyscript to cache the passphrase, so that I have to enter it only once.
As far
Hello,
I have several LUKS encrypted volumes that use the same
passphrase. Before switching to systemd, I have used the decrypt_keyctl
keyscript to cache the passphrase, so that I have to enter it only once.
As far as I can tell, the systemd cryptsetup generator is ignoring the
keyscript option