lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sun, 12 May 2019 17:23:16 -0700
To:     Dominik Brodowski <>,
        Mimi Zohar <>
CC:     Roberto Sassu <>,,,,,,,,,,,,,,,
Subject: Re: [PATCH v2 0/3] initramfs: add support for xattrs in the initial ram disk

On May 12, 2019 8:31:05 AM PDT, Dominik Brodowski <> wrote:
>On Sun, May 12, 2019 at 03:18:16AM -0700, wrote:
>> > Couldn't this parsing of the .xattr-list file and the setting of
>the xattrs
>> > be done equivalently by the initramfs' /init? Why is kernel
>> > actually required here?
>> There are a lot of things that could/should be done that way...
>Indeed... so why not try to avoid adding more such "things", and
>them in userspace (or in a fork_usermode_blob)?
>On Sun, May 12, 2019 at 08:52:47AM -0400, Mimi Zohar wrote:
>> It's too late.  The /init itself should be signed and verified.
>Could you elaborate a bit more about the threat model, and why
>this to the initramfs is too late?
>	Dominik

I tried over 10 years ago to make exactly that happen... it was called the klibc project. Linus turned it down because he felt that it didn't provide enough immediate benefit to justify the complexity, which of course creates the thousand-cuts problem: there will never be *one single* event that *by itself* justifies the transition.
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Powered by blists - more mailing lists