From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/28788] New: consider low-security secureboot mode
Date: Mon, 17 Jan 2022 18:56:23 +0000 [thread overview]
Message-ID: <bug-28788-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=28788
Bug ID: 28788
Summary: consider low-security secureboot mode
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
Assignee: systemtap at sourceware dot org
Reporter: fche at redhat dot com
Target Milestone: ---
It seems like many folks running secureboot machines who also wish to run stap
lkm scripts find the stap-server based signing machinery onerous - and its
extra security unnecessary. We should investigate a stap command line option
where it performs module signing / mok stuff in a self-sufficient manner.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-01-17 18:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 18:56 fche at redhat dot com [this message]
2022-01-17 20:50 ` [Bug translator/28788] consider low-security stap-server-less " fche at redhat dot com
2022-01-18 12:36 ` fweimer at redhat dot com
2022-04-25 18:16 ` scox at redhat dot com
2022-04-25 18:18 ` scox 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-28788-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).