public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/26665] New: secureboot stap-server matching breaks if non-stap MOK is already enrolled
Date: Fri, 25 Sep 2020 16:00:30 +0000	[thread overview]
Message-ID: <bug-26665-6586@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=26665

            Bug ID: 26665
           Summary: secureboot stap-server matching breaks if non-stap MOK
                    is already enrolled
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
          Assignee: systemtap at sourceware dot org
          Reporter: fche at redhat dot com
  Target Milestone: ---

nss_get_or_keep_compatible_server_info() filters out stap servers that lack mok
keys that the client knows of, on the assumption that the only mok keys in the
system could be systemtap ones.  But that's not the case.  We need to exclude
local mok's that are systemtap-unrelated.  And in the case where there is no
matching server (say, an old stap-server ran that generated our mok, but is now
dead), we need to give users recovery instructions (drop the local mok and/or
try another server).

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2020-09-25 16:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-25 16:00 fche at redhat dot com [this message]
2020-09-30 14:11 ` [Bug runtime/26665] " fche at redhat dot com
2020-11-10  1:39 ` fche at redhat dot com

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=bug-26665-6586@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).