Hi Christoph,
On Mon, 27 Jan 2020 at 07:23:02 +0100, Christoph Biedl wrote:
> As far as I understand however, while such a situation _can_ happen, it
> is not very likely.
FWIW our last heavy refactoring was in spring/summer 2018. We obviously
won't change the internal interface just “for fun”,
Control: tag 891410 pending
Guilhem Moulin wrote...
> Hmm. I guess I'm part of the problem since I haven't found time to help
> with this unfortunately, but on a quick look it appears that my comments
> from msg#27 and msg#32 still hold.
>
> cryptsetup's initramfs integration isn't part of crypt
On Wed, 22 Jan 2020 at 14:37:54 -0600, Mario Limonciello wrote:
> Would you mind suggesting something upstream with the relevant changes
> that make sense?
As written earlier in this bug our public interface for this kind of
things is to use keyscripts. See crypttab(5) for the few environment
var
I think that upstream would be happy to switch to a "public" interface in
the future. Would you mind suggesting something upstream with the relevant
changes that make sense?
On Mon, Jan 20, 2020 at 7:52 AM Guilhem Moulin wrote:
> On Mon, 20 Jan 2020 at 07:12:37 -0600, Mario Limonciello wrote:
>
On Mon, 20 Jan 2020 at 07:12:37 -0600, Mario Limonciello wrote:
> FYI, the newly released version 12 has initramfs support.
Hmm. I guess I'm part of the problem since I haven't found time to help
with this unfortunately, but on a quick look it appears that my comments
from msg#27 and msg#32 still
FYI, the newly released version 12 has initramfs support.
On Sun, 07 Oct 2018 15:07:32 +0200 "Hein, Jochen" wrote:
> Hello again,
>
> Am 2018-07-02 21:05, schrieb Christoph Biedl:
> > Thanks for reminding me, it's on radar - but given the discussion
> > hasn't
> > been finished yet I'd prefer to wait until this is part of another
> > clevis release. If yo
Hello again,
Am 2018-07-02 21:05, schrieb Christoph Biedl:
Thanks for reminding me, it's on radar - but given the discussion
hasn't
been finished yet I'd prefer to wait until this is part of another
clevis release. If you'd like to have it cherry-picked so people can
start playing with it, let
On Mon, 23 Jul 2018 at 18:32:44 +0200, Guilhem Moulin wrote:
> * /scripts/local-top/clevis: some bits look quite brittle, for
> instance
>
> psinfo=$(ps) # Doing this so I don't end up matching myself
> echo "$psinfo" | awk "/$cryptkeyscript/ { print \$1 }" | \
>
> and
>
> local $(gr
Hi,
On Sun, 25 Feb at 2018 12:01:02 +0100, Christoph Biedl wrote:
> Now I'm somewhat stuck. If people with knowledge in initramfs and
> especially the unlocking process there using cryptsetup could provide
> some input, I'd be glad.
Given that cryptsetup's initramfs integration is not authored by
Christoph Biedl writes:
> Thanks for reminding me, it's on radar - but given the discussion hasn't
> been finished yet I'd prefer to wait until this is part of another
> clevis release. If you'd like to have it cherry-picked so people can
> start playing with it, let me know.
I've no idea when t
tags 891410 -help pending
thanks
Jochen Hein wrote...
> please have a look at https://github.com/latchset/clevis/pull/35
> I've used the scripts from https://github.com/latchset/clevis/pull/18,
> where I added my comments/diff for Debian.
>
> I guess that the updated pull request is a better sta
Hello,
please have a look at https://github.com/latchset/clevis/pull/35
I've used the scripts from https://github.com/latchset/clevis/pull/18,
where I added my comments/diff for Debian.
I guess that the updated pull request is a better start now.
Hope this helps.
Jochen
--
This space is inte
Package: src:clevis
Version: 8-1
Severity: normal
Tags: help
As of now, clevis provides initrd for dracut only. While dracut is
available in Debian and automated unlocking of the root filesystem
works quite well, Debian's default initrd is initramfs and it would
certainly increase acceptance of cl
14 matches
Mail list logo
