From: "rfhn.fhbrrjnzeneqpf at noclue dot notk.org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/30978] debuginfod-client security: optionally(?) verify downloaded binaries
Date: Tue, 17 Oct 2023 22:24:46 +0000 [thread overview]
Message-ID: <bug-30978-10460-ErsmFcylbw@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30978-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30978
--- Comment #3 from Dominique Martinet <rfhn.fhbrrjnzeneqpf at noclue dot notk.org> ---
Interesting, thanks for the link!
The implementation hurdle is a bit higher than updating the already-used
objcopy command I was suggesting (won't be available for distros like debian
that don't ship IMA data), but if available it's definitely a good alternative.
As I understand that bz, the signature would be verified if available
regardless of the kernel IMA setting, so for all fedora users as soon as it's
available in debuginfod?
I'll check the bz in more details and patch as time permits (probably next
week)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-10-17 22:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 19:20 [Bug debuginfod/30978] New: " rfhn.fhbrrjnzeneqpf at noclue dot notk.org
2023-10-17 19:32 ` [Bug debuginfod/30978] " rfhn.fhbrrjnzeneqpf at noclue dot notk.org
2023-10-17 22:07 ` fche at redhat dot com
2023-10-17 22:24 ` rfhn.fhbrrjnzeneqpf at noclue dot notk.org [this message]
2023-10-18 20:01 ` fche at redhat dot com
2023-10-19 0:01 ` rfhn.fhbrrjnzeneqpf at noclue dot notk.org
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-30978-10460-ErsmFcylbw@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@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).