From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 52866-done@debbugs.gnu.org
Subject: [bug#52866] maintenance: Add a crash dump service.
Date: Tue, 08 Feb 2022 10:53:07 +0100 [thread overview]
Message-ID: <87o83hbs70.fsf@gnu.org> (raw)
In-Reply-To: <87pmo5cjo1.fsf@gnu.org> (Mathieu Othacehe's message of "Wed, 02 Feb 2022 17:33:50 +0100")
Hi,
Mathieu Othacehe <othacehe@gnu.org> skribis:
>> OK (I didn’t know it was already deployed!). What if we just put the
>> uploaded file in a directory and let nginx provide a directory index and
>> all? Anyway, given the target audience, it doesn’t have to be fancy.
>
> Heh, it was deployed for testing purposes and is now just committed. I
> also considered the nginx directory index but I feel like the current
> approach gives us more flexibility.
>
>> The message should allow for informed consent. Thus it should explain
>> what the risks are (“Logs may contain sensitive information such as …”,
>> “Logs are eventually publicly visible, but IP addresses are not logged”,
>> etc.) and/or it should let users screen all the logs.
>
> Josselin did add the possibility to consult and edit the log files
> before creating the crash dump.
>
>> As discussed the other day on IRC, to make sure the backtrace does not
>> contain passwords, we could define a record type for “secrets”, which
>> would basically just “box” strings such as passwords. That record
>> type’s printer would just print #<secret 0123abcd>. See
>> <file-system-label> for an example.
>
> Also implemented by Josselin.
Well done, thank you!
Ludo’.
prev parent reply other threads:[~2022-02-08 10:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 9:16 [bug#52866] maintenance: Add a crash dump service Mathieu Othacehe
2021-12-29 17:37 ` zimoun
2022-01-05 21:13 ` Ludovic Courtès
2022-01-06 8:22 ` Mathieu Othacehe
2022-01-07 11:16 ` Josselin Poiret via Guix-patches via
2022-01-11 13:10 ` Ludovic Courtès
2022-02-02 16:33 ` bug#52866: " Mathieu Othacehe
2022-02-08 9:53 ` Ludovic Courtès [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o83hbs70.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=52866-done@debbugs.gnu.org \
--cc=othacehe@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).