From: Lee Fisher <lee@preossec.com>
To: openbmc@lists.ozlabs.org
Subject: Re: Secure boot/signed images and GPL code
Date: Tue, 3 Nov 2020 13:21:53 -0800 [thread overview]
Message-ID: <c3da59d4-b312-2372-0bfd-77014fb1fba6@preossec.com> (raw)
In-Reply-To: <20201103205600.GA38269@patrickw3-mbp.lan.stwcx.xyz>
> Does secure boot on the BMC (I think for my question it doesn't matter
> where the hardware root of trust is - it could be on the BMC or an
external
> chip) or signed images deprive users of rights associated with code in
> OpenBMC that is GPL licensed? [...]
In this thread I don't see any reference to OpenBMC use of the existing
Shim[1] -- the current Linux UEFI Secure Boot solution to address these
legal issues. It seems that if the Shim can't work for OpenBMC case,
then OpenBMC could create a similar Shim-like widget. FYI, there's a
Shim mailing list.
[1] https://github.com/rhboot/shim
https://lists.freedesktop.org/mailman/listinfo/shim-review
next prev parent reply other threads:[~2020-11-03 21:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 17:20 Secure boot/signed images and GPL code Deepak Kodihalli
2020-11-03 20:56 ` Patrick Williams
2020-11-03 21:21 ` Lee Fisher [this message]
2020-11-04 13:31 ` Patrick Williams
2020-11-03 22:59 ` Doman, Jonathan
2020-11-06 17:19 ` Vernon Mauery
2020-11-06 21:24 ` Joseph Reynolds
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=c3da59d4-b312-2372-0bfd-77014fb1fba6@preossec.com \
--to=lee@preossec.com \
--cc=openbmc@lists.ozlabs.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).