On Fri, 29.05.15 15:45, Dimitri John Ledkov ([email protected]) wrote:
> On 29 May 2015 at 11:17, <[email protected]> wrote: > > From: Harald Hoyer <[email protected]> > > > > If cryptsetup is called with a source device as argv[3], then craft the > > ID for the password agent with a unique device path. > > > > I'm not sure why this is needed... if the device path is not good > enough, there is also luks UUID header. In Ubuntu we display the full > cryptsetup UUID in plymouth, but that's fairly cosmetic. > If the path is not good enough, maj/min are a bit pointless and you > really probably want the luks UUID then. Harald actually convinced me now that this is useful indeed, simply to ensure that if multiple invocations of systemd-cryptsetup using different device aliases actually result in the same id used in the password file. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
