On Thu, Sep 12, 2013 at 12:10 PM, Harald Hoyer harald.ho...@gmail.com wrote:
On 09/11/2013 05:35 PM, Lennart Poettering wrote:
On Mon, 19.08.13 00:15, Tom Gundersen (t...@jklm.no) wrote:
The main usecase for this is to make it possible to use cryptsetup in
the initrd without it having to
On Fri, 13.09.13 11:52, Tom Gundersen (t...@jklm.no) wrote:
On Thu, Sep 12, 2013 at 12:10 PM, Harald Hoyer harald.ho...@gmail.com wrote:
On 09/11/2013 05:35 PM, Lennart Poettering wrote:
On Mon, 19.08.13 00:15, Tom Gundersen (t...@jklm.no) wrote:
The main usecase for this is to make it
On Fri, Sep 13, 2013 at 6:18 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Fri, 13.09.13 11:52, Tom Gundersen (t...@jklm.no) wrote:
On Thu, Sep 12, 2013 at 12:10 PM, Harald Hoyer harald.ho...@gmail.com
wrote:
On 09/11/2013 05:35 PM, Lennart Poettering wrote:
On Mon, 19.08.13
On 09/11/2013 05:35 PM, Lennart Poettering wrote:
On Mon, 19.08.13 00:15, Tom Gundersen (t...@jklm.no) wrote:
The main usecase for this is to make it possible to use cryptsetup in
the initrd without it having to include a host-specific /etc/crypttab.
Hmm, I contrast to Harald I think
On Mon, 19.08.13 00:15, Tom Gundersen (t...@jklm.no) wrote:
The main usecase for this is to make it possible to use cryptsetup in
the initrd without it having to include a host-specific /etc/crypttab.
Hmm, I contrast to Harald I think adding luks.options= would actually be
OK.
I don't think
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/19/2013 07:30 PM, Thomas Bächler wrote:
Am 19.08.2013 13:25, schrieb Thomas Bächler:
Am 19.08.2013 11:58, schrieb Harald Hoyer:
On 08/19/2013 11:21 AM, Thomas Bächler wrote:
Am 19.08.2013 10:34, schrieb Harald Hoyer:
Hmm, the naming
On 08/18/2013 06:15 PM, Tom Gundersen wrote:
The main usecase for this is to make it possible to use cryptsetup in
the initrd without it having to include a host-specific /etc/crypttab.
Cc: Harald Hoyer har...@redhat.com
Tested-by: Thomas Bächler tho...@archlinux.org
---
Hi guys,
This
Am 19.08.2013 10:34, schrieb Harald Hoyer:
Hmm, the naming luks.options is IMHO poorly chosen. options as an option
name... hmm. Also crypttab can contain more encryption modes, than LUKS.
If you want to reflect crypttab, why not specify something like:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/19/2013 11:21 AM, Thomas Bächler wrote:
Am 19.08.2013 10:34, schrieb Harald Hoyer:
Hmm, the naming luks.options is IMHO poorly chosen. options as an
option name... hmm. Also crypttab can contain more encryption modes, than
LUKS.
If you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am 19.08.2013 11:58, schrieb Harald Hoyer:
On 08/19/2013 11:21 AM, Thomas Bächler wrote:
Am 19.08.2013 10:34, schrieb Harald Hoyer:
Hmm, the naming luks.options is IMHO poorly chosen. options
as an option name... hmm. Also crypttab can contain
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am 19.08.2013 13:25, schrieb Thomas Bächler:
Am 19.08.2013 11:58, schrieb Harald Hoyer:
On 08/19/2013 11:21 AM, Thomas Bächler wrote:
Am 19.08.2013 10:34, schrieb Harald Hoyer:
Hmm, the naming luks.options is IMHO poorly chosen.
options as an
The main usecase for this is to make it possible to use cryptsetup in
the initrd without it having to include a host-specific /etc/crypttab.
Cc: Harald Hoyer har...@redhat.com
Tested-by: Thomas Bächler tho...@archlinux.org
---
Hi guys,
This allows us to use systemd in the initrd for encrypted
12 matches
Mail list logo
