From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/27758] security idea: DEBUGINFOD_VERIFY mode
Date: Tue, 20 Apr 2021 18:23:58 +0000 [thread overview]
Message-ID: <bug-27758-10460-xIw9tqsQwf@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27758-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27758
--- Comment #2 from Frank Ch. Eigler <fche at redhat dot com> ---
Yeah. It may comfort those who are worried about the integrity of their
previously downloaded cached files, but is not robust against local attacker
who currently has control over the filesystem or processes.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-04-20 18:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 15:22 [Bug debuginfod/27758] New: " fche at redhat dot com
2021-04-20 18:18 ` [Bug debuginfod/27758] " zbyszek at in dot waw.pl
2021-04-20 18:23 ` fche at redhat dot com [this message]
2021-04-21 0:15 ` vt at altlinux dot org
2021-04-21 9:35 ` fweimer at redhat dot com
2021-04-21 14:09 ` fche at redhat dot com
2021-05-20 2:13 ` 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-27758-10460-xIw9tqsQwf@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).