all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <othacehe@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 52866-done@debbugs.gnu.org
Subject: bug#52866: maintenance: Add a crash dump service.
Date: Wed, 02 Feb 2022 17:33:50 +0100	[thread overview]
Message-ID: <87pmo5cjo1.fsf@gnu.org> (raw)
In-Reply-To: <875yqqv2n3.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 11 Jan 2022 14:10:56 +0100")


Hey,

> 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.

Closing this one,

Thanks,

Mathieu




  reply	other threads:[~2022-02-02 17:43 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       ` Mathieu Othacehe [this message]
2022-02-08  9:53         ` Ludovic Courtès

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=87pmo5cjo1.fsf@gnu.org \
    --to=othacehe@gnu.org \
    --cc=52866-done@debbugs.gnu.org \
    --cc=ludo@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.