From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/27784] New: debuginfod client-use notification
Date: Tue, 27 Apr 2021 18:24:21 +0000 [thread overview]
Message-ID: <bug-27784-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27784
Bug ID: 27784
Summary: debuginfod client-use notification
Product: elfutils
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: debuginfod
Assignee: unassigned at sourceware dot org
Reporter: fche at redhat dot com
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
There have been concerns that if debuginfod* client facilities are turned on by
default in a system, a user may have no idea that they are exposing themselves
to the possibility of Bad data flowing down from debuginfod servers. There was
a suggestion that if we (something?) were to notify users, this could be
enough.
Let's consider extending debuginfod-client.c with a small notification option.
We probably can't get away with anything interactive in a low level library,
but this simple trick might work:
- upon each request to debuginfod-client, check for existence of a file
$DEBUGINFOD_CACHE/notified_p
- if does not exist, and isatty(stdout), then print a quick notification
message to the user, sleep a second or two, touch that notified_p file, and
continue
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-04-27 18:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 18:24 fche at redhat dot com [this message]
2021-04-27 18:24 ` [Bug debuginfod/27784] debuginfod first-client-use notification fche at redhat dot com
2021-05-20 2:12 ` 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-27784-10460@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).