All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Florian Weimer <fweimer@redhat.com>, Kyle McMartin <jkkm@jkkm.org>
Cc: dhowells@redhat.com, Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	mtk.manpages@gmail.com, mcgrof@kernel.org,
	johannes@sipsolutions.net, linux-man@vger.kernel.org,
	keyrings@vger.kernel.org, linux-security-module@vger.kernel.org,
	linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Draft manpage explaining kernel lockdown
Date: Thu, 05 Oct 2017 13:20:00 +0000	[thread overview]
Message-ID: <9488.1507209600@warthog.procyon.org.uk> (raw)
In-Reply-To: <3765ad08-2c73-7285-02e1-e04f31dde3fd@redhat.com>

Florian Weimer <fweimer@redhat.com> wrote:

> > Lockdown is typically enabled during boot and may be terminated, if
> > configured, by typing a special key combination on a directly attached
> > physical keyboard.
> 
> Does this include a Bluetooth keyboard (which might not actually exist and
> might in reality be another server in the same rack, of course).

Ummm...  Interesting question.  I'm not sure how to tell.  I think it
shouldn't include a Bluetooth keyboard, and not even a serial console.

David

WARNING: multiple messages have this Message-ID (diff)
From: David Howells <dhowells@redhat.com>
To: Florian Weimer <fweimer@redhat.com>, Kyle McMartin <jkkm@jkkm.org>
Cc: dhowells@redhat.com, Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	mtk.manpages@gmail.com, mcgrof@kernel.org,
	johannes@sipsolutions.net, linux-man@vger.kernel.org,
	keyrings@vger.kernel.org, linux-security-module@vger.kernel.org,
	linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Draft manpage explaining kernel lockdown
Date: Thu, 05 Oct 2017 14:20:00 +0100	[thread overview]
Message-ID: <9488.1507209600@warthog.procyon.org.uk> (raw)
In-Reply-To: <3765ad08-2c73-7285-02e1-e04f31dde3fd@redhat.com>

Florian Weimer <fweimer@redhat.com> wrote:

> > Lockdown is typically enabled during boot and may be terminated, if
> > configured, by typing a special key combination on a directly attached
> > physical keyboard.
> 
> Does this include a Bluetooth keyboard (which might not actually exist and
> might in reality be another server in the same rack, of course).

Ummm...  Interesting question.  I'm not sure how to tell.  I think it
shouldn't include a Bluetooth keyboard, and not even a serial console.

David

WARNING: multiple messages have this Message-ID (diff)
From: dhowells@redhat.com (David Howells)
To: linux-security-module@vger.kernel.org
Subject: Draft manpage explaining kernel lockdown
Date: Thu, 05 Oct 2017 14:20:00 +0100	[thread overview]
Message-ID: <9488.1507209600@warthog.procyon.org.uk> (raw)
In-Reply-To: <3765ad08-2c73-7285-02e1-e04f31dde3fd@redhat.com>

Florian Weimer <fweimer@redhat.com> wrote:

> > Lockdown is typically enabled during boot and may be terminated, if
> > configured, by typing a special key combination on a directly attached
> > physical keyboard.
> 
> Does this include a Bluetooth keyboard (which might not actually exist and
> might in reality be another server in the same rack, of course).

Ummm...  Interesting question.  I'm not sure how to tell.  I think it
shouldn't include a Bluetooth keyboard, and not even a serial console.

David
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2017-10-05 13:20 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-05 11:00 Draft manpage explaining kernel lockdown David Howells
2017-10-05 11:00 ` David Howells
2017-10-05 11:00 ` David Howells
2017-10-05 11:07 ` Johannes Berg
2017-10-05 11:07   ` Johannes Berg
2017-10-05 11:07   ` Johannes Berg
2017-10-05 13:16   ` David Howells
2017-10-05 13:16     ` David Howells
2017-10-05 13:16     ` David Howells
2017-10-05 18:29   ` Randy Dunlap
2017-10-05 18:29     ` Randy Dunlap
2017-10-05 18:29     ` Randy Dunlap
2017-10-05 13:53 ` Ard Biesheuvel
2017-10-05 13:53   ` Ard Biesheuvel
2017-10-05 13:53   ` Ard Biesheuvel
2017-10-18  8:21 ` Michael Kerrisk (man-pages)
2017-10-18  8:21   ` Michael Kerrisk (man-pages)
2017-10-18  8:21   ` Michael Kerrisk (man-pages)
     [not found] ` <7969.1507201224-S6HVgzuS8uM4Awkfq6JHfwNdhmdF6hFW@public.gmane.org>
2017-10-05 12:33   ` Florian Weimer
2017-10-05 12:33     ` Florian Weimer
2017-10-05 12:33     ` Florian Weimer
2017-10-05 12:33     ` Florian Weimer
2017-10-05 13:20     ` David Howells [this message]
2017-10-05 13:20       ` David Howells
2017-10-05 13:20       ` David Howells
2017-10-06  7:46   ` joeyli
2017-10-06  7:46     ` joeyli
2017-10-06  7:46     ` joeyli
2017-10-06  7:46     ` joeyli
2017-11-15 21:12   ` Pavel Machek
2017-11-15 21:12     ` Pavel Machek
2017-11-15 21:12     ` Pavel Machek

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=9488.1507209600@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=fweimer@redhat.com \
    --cc=jkkm@jkkm.org \
    --cc=johannes@sipsolutions.net \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=mtk.manpages@gmail.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.