Okay, thank you. I see where the existing service files are.
On Wed, Oct 19, 2016 at 4:19 PM, Lennart Poettering
wrote:
> On Wed, 19.10.16 16:10, Ryan Castellucci (ryan.castellucci+systemd-
> [email protected]) wrote:
>
> > It looks like my use case could be supported with a "Password Agent", and
On Wed, 19.10.16 16:10, Ryan Castellucci
([email protected]) wrote:
> It looks like my use case could be supported with a "Password Agent", and
> it seems that it would be possible to wrap the existing keyscript stuff
> (though the interface is much more complicated).
>
>
It looks like my use case could be supported with a "Password Agent", and
it seems that it would be possible to wrap the existing keyscript stuff
(though the interface is much more complicated).
How should a password agent be started? Is there a way to disable
particular password agents?
On Wed,
On Wed, 19.10.16 15:28, Ryan Castellucci
([email protected]) wrote:
> Systemd broke a use case that people were actively using, and cryptsetup
> comes with scripts to support.
Humm, the keyscript thing was a Debian-specific extension. It was
never supported on systemd or a
Systemd broke a use case that people were actively using, and cryptsetup
comes with scripts to support.
There were complaints about this four years ago, you rejected a patch that
would have resolved it, and it still has not been addressed.
If you won't merge the patch that addresses this, can you
On Wed, 19.10.16 11:20, Ryan Castellucci
([email protected]) wrote:
> What will it take to get keyscript support in systemd-cryptsetup fixed?
>
> This is a nasty regression for people who were using that functionality,
> and it necessitating some pretty ugly workarounds. I
