From: Borislav Petkov <bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org>
To: David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Cc: "John W. Linville"
<linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: UEFI Plugfest 2013 -- New Orleans
Date: Mon, 19 Aug 2013 17:17:21 +0200 [thread overview]
Message-ID: <20130819151721.GA5223@pd.tnic> (raw)
In-Reply-To: <1376900735.2322.26.camel-Fexsq3y4057IgHVZqg5X0TlWvGAXklZc@public.gmane.org>
On Mon, Aug 19, 2013 at 09:25:35AM +0100, David Woodhouse wrote:
> Hm. It would be really useful to have a kernel build option which
> *disables* all the workarounds we've ever put in for broken firmware.
Yeah, cool!
I wonder if we could reach a high double-digit percentage of machines
not booting/barfing on such a clean kernel.
While at it, can we please replace the fw with coreboot? :-)
> Every deviation from the spec (or common sense), however minor, should
> show up as a clear failure. Even the ones we *have* been able to work
> around, because we still want them *fixed*.
>
> And there's a school of thought that says we should brick as many
> Samsung machines as possible,
Yep, and there's the rooted secure boot asus f*ckup which we should also
advertize while booting, enabling people to use it:
https://www.blackhat.com/us-13/archives.html#Bulygin
/me LOLs ominously...
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org
Subject: Re: UEFI Plugfest 2013 -- New Orleans
Date: Mon, 19 Aug 2013 17:17:21 +0200 [thread overview]
Message-ID: <20130819151721.GA5223@pd.tnic> (raw)
In-Reply-To: <1376900735.2322.26.camel@shinybook.infradead.org>
On Mon, Aug 19, 2013 at 09:25:35AM +0100, David Woodhouse wrote:
> Hm. It would be really useful to have a kernel build option which
> *disables* all the workarounds we've ever put in for broken firmware.
Yeah, cool!
I wonder if we could reach a high double-digit percentage of machines
not booting/barfing on such a clean kernel.
While at it, can we please replace the fw with coreboot? :-)
> Every deviation from the spec (or common sense), however minor, should
> show up as a clear failure. Even the ones we *have* been able to work
> around, because we still want them *fixed*.
>
> And there's a school of thought that says we should brick as many
> Samsung machines as possible,
Yep, and there's the rooted secure boot asus f*ckup which we should also
advertize while booting, enabling people to use it:
https://www.blackhat.com/us-13/archives.html#Bulygin
/me LOLs ominously...
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-08-19 15:17 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 15:20 UEFI Plugfest 2013 -- New Orleans John W. Linville
2013-08-16 15:20 ` John W. Linville
[not found] ` <20130816152030.GL2133-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2013-08-17 0:44 ` James Bottomley
2013-08-17 0:44 ` James Bottomley
2013-08-19 8:25 ` David Woodhouse
[not found] ` <1376900735.2322.26.camel-Fexsq3y4057IgHVZqg5X0TlWvGAXklZc@public.gmane.org>
2013-08-19 12:55 ` Matthew Garrett
2013-08-19 12:55 ` Matthew Garrett
[not found] ` <20130819125507.GA19093-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2013-08-19 15:22 ` James Bottomley
2013-08-19 15:22 ` James Bottomley
2013-08-19 16:00 ` Matthew Garrett
[not found] ` <20130819160018.GA22532-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2013-08-19 17:02 ` James Bottomley
2013-08-19 17:02 ` James Bottomley
[not found] ` <1376931775.2069.46.camel-sFMDBYUN5F8GjUHQrlYNx2Wm91YjaHnnhRte9Li2A+AAvxtiuMwx3w@public.gmane.org>
2013-08-19 17:21 ` Matthew Garrett
2013-08-19 17:21 ` Matthew Garrett
2013-08-19 17:38 ` James Bottomley
[not found] ` <1376933926.2069.52.camel-sFMDBYUN5F8GjUHQrlYNx2Wm91YjaHnnhRte9Li2A+AAvxtiuMwx3w@public.gmane.org>
2013-08-19 17:47 ` Matthew Garrett
2013-08-19 17:47 ` Matthew Garrett
2013-08-19 20:09 ` David Woodhouse
2013-08-19 20:09 ` David Woodhouse
[not found] ` <1376942994.2322.39.camel-Fexsq3y4057IgHVZqg5X0TlWvGAXklZc@public.gmane.org>
2013-08-19 20:19 ` Matthew Garrett
2013-08-19 20:19 ` Matthew Garrett
[not found] ` <20130819201952.GA28740-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2013-08-19 20:21 ` David Woodhouse
2013-08-19 20:21 ` David Woodhouse
[not found] ` <1376943671.2322.40.camel-Fexsq3y4057IgHVZqg5X0TlWvGAXklZc@public.gmane.org>
2013-08-19 20:39 ` Matthew Garrett
2013-08-19 20:39 ` Matthew Garrett
[not found] ` <20130819203937.GA28967-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2013-08-19 21:06 ` David Woodhouse
2013-08-19 21:06 ` David Woodhouse
[not found] ` <1376946411.5087.2.camel-Fexsq3y4057IgHVZqg5X0TlWvGAXklZc@public.gmane.org>
2013-08-19 21:30 ` Matthew Garrett
2013-08-19 21:30 ` Matthew Garrett
2013-09-02 7:42 ` Alex Elsayed
2013-09-02 6:23 ` Matt Fleming
2013-09-02 6:23 ` Matt Fleming
2013-08-19 15:17 ` Borislav Petkov [this message]
2013-08-19 15:17 ` Borislav Petkov
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=20130819151721.GA5223@pd.tnic \
--to=bp-gina5biwoiwzqb+pc5nmwq@public.gmane.org \
--cc=dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.