Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: EFI Secure Boot Build Support
Date: Fri, 21 Jun 2019 07:29:54 +0200	[thread overview]
Message-ID: <20190621052954.wO5C9YRwSYhMn57XFtDtn_BkSHeYswk4tVGpN8STyso@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12495@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 2045 bytes --]

New comment by congdanhqx on void-packages repository

https://github.com/void-linux/void-packages/issues/12495#issuecomment-504295085
Comment:
On June 20, 2019 10:38:25 PM UTC, andkem <notifications@github.com> wrote:

>they don't, as you point out, sign the initrd or provide tools for

The sbsigntools couldn't sign the initrd itself, it can sign the efi executable (EFIStub enabled kerbel, refind, grub) only.

If I understand other comments correctly,  grub signs kernel and initrd with gpg.

>actually generating keys.

The efi signing-key generation is done by openssl and efitools, IIRC, I didn't put the key generator script into the installation because I weren't sure what should be done with the manufacture's key that's existed in EFI firmware? Should we concatenate that key with our newly generated key or we should simply throw it away or we should give users a choice?

I don't know about the key generation for GRUB, is it a gpg key? What is our expectation for this? Or we should skip signing if there're no gpg key?

>There were some block of the hook that had a
>comment stating it was untested, iirc.

The untested part is about the EFI_SIGN_ENGINE,
That option is used for some specific EFI firmwares,
I don't have those firmwares, hence, I couldn't test.

>for the week-end so I cannot check.
>
>For a secure boot solution that isn't trivial (well almost) to
>circumvent we need both kernel and initrd to be signed. We also need
>the root file system to either be signed and read only, ex. using
>dm-verity, or encrypted. I'd suggest that telling people to encrypt
>should be enough, since a read only root won't really work with Void
>the way it is currently structured.
>
>The main point to make for using Grub instead of a pure EFI boot is
>that we could support having the boot partition encrypted. Even with
>signed binaries, there are attacks that can be mitigated by having it

Agree, different threat models have different mitigations.



-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.


  parent reply	other threads:[~2019-06-21  5:29 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-16 18:33 [ISSUE] " voidlinux-github
2019-06-16 18:36 ` voidlinux-github
2019-06-16 19:34 ` voidlinux-github
2019-06-17 18:24 ` voidlinux-github
2019-06-17 18:39 ` voidlinux-github
2019-06-18 18:55 ` voidlinux-github
2019-06-18 18:56 ` voidlinux-github
2019-06-18 18:57 ` voidlinux-github
2019-06-20 11:17 ` voidlinux-github
2019-06-20 11:20 ` voidlinux-github
2019-06-20 11:22 ` voidlinux-github
2019-06-20 11:26 ` voidlinux-github
2019-06-20 22:38 ` voidlinux-github
2019-06-20 22:39 ` voidlinux-github
2019-06-20 22:40 ` voidlinux-github
2019-06-21  5:29 ` voidlinux-github [this message]
2019-07-01 15:58 ` voidlinux-github
2019-10-03 22:10 ` voidlinux-github
2020-07-27 14:20 ` unixandria-xda
2020-07-27 14:57 ` sgn
2020-07-28  5:50 ` ericonr
2020-07-28  6:02 ` sgn
2022-04-15  2:12 ` github-actions
2022-04-29  2:13 ` [ISSUE] [CLOSED] " github-actions
2022-07-28  4:47 ` dm17
2023-01-09  6:27 ` thegarlynch
2024-02-11 15:08 ` Izooc

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190621052954.wO5C9YRwSYhMn57XFtDtn_BkSHeYswk4tVGpN8STyso@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).