From: Jann Horn <jann@thejh.net>
To: Solar Designer <solar@openwall.com>
Cc: kernel-hardening@lists.openwall.com
Subject: Re: [kernel-hardening] Any artists around?
Date: Thu, 6 Oct 2016 04:27:01 +0200 [thread overview]
Message-ID: <20161006022701.GX14666@pc.thejh.net> (raw)
In-Reply-To: <20161005223220.GA6533@openwall.com>
[-- Attachment #1: Type: text/plain, Size: 1710 bytes --]
On Thu, Oct 06, 2016 at 12:32:20AM +0200, Solar Designer wrote:
> On Mon, Oct 03, 2016 at 12:59:31PM -0700, Kees Cook wrote:
> > On Mon, Oct 3, 2016 at 12:34 PM, Solar Designer <solar@openwall.com> wrote:
> > > On Mon, Oct 03, 2016 at 12:16:07PM -0700, Kees Cook wrote:
> > >> Does anyone have some suggestions or sketches for a logo we could use?
> > >
> > > How about a bikeshed? It would convey how hardening is not "perfect
> > > security", and ack the irony of spending time on discussing a logo.
> > > I don't even have a preference as to which color the bikeshed should be.
> >
> > Haha, yes, exactly. This is the opening image I used in my slides
> > covering the uid-0/ring-0 lockdown series at LSS on 2014:
> >
> > https://outflux.net/bikeshed.jpg
>
> Oh, cool. Meanwhile, my Twitter poll ended in favor of bikeshed:
>
> https://twitter.com/solardiz/status/783033528736940032
>
> "What should (Linux) Kernel Self Protection Project's logo be?
>
> 32% A fancy penguin
> 42% A bikeshed
> 7% Other (please tweet what)
> 19% No logo
>
> 116 votes"
>
> A bikeshed would also ack the grsecurity project's opinion (as I
> understand it) that trying to upstream hardening changes (through the
> hoops) is sort of bikeshedding (in comparison with having made such
> changes) or that the typical initial response (those hoops) is
> bikeshedding, and that some of those changes (not in grsecurity) are a
> bikeshed on their own. This shouldn't stop us, but we can troll
> ourselves a bit by ack'ing this dissenting opinion in the logo. ;-)
A bikeshed sounds good, but maybe we can split the bikeshed image into
a few tiles and rearrange them? You know, kASLR?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-10-06 2:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 19:16 [kernel-hardening] Any artists around? Kees Cook
2016-10-03 19:21 ` Schaufler, Casey
2016-10-03 19:27 ` Yves-Alexis Perez
2016-10-03 20:00 ` Kees Cook
2016-10-05 7:08 ` James Morris
2016-10-06 21:30 ` Kees Cook
2016-10-03 19:34 ` Solar Designer
2016-10-03 19:59 ` Kees Cook
2016-10-05 22:32 ` Solar Designer
2016-10-06 2:24 ` Theodore Ts'o
2016-10-06 6:50 ` Schaufler, Casey
2016-10-06 21:29 ` Kees Cook
2016-10-06 2:27 ` Jann Horn [this message]
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=20161006022701.GX14666@pc.thejh.net \
--to=jann@thejh.net \
--cc=kernel-hardening@lists.openwall.com \
--cc=solar@openwall.com \
/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.