all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 59383@debbugs.gnu.org
Subject: [bug#59383] [PATCH] doc: Call out potential for downgrade attacks with time-machine.
Date: Sat, 19 Nov 2022 18:39:50 +0100	[thread overview]
Message-ID: <87wn7qn8rd.fsf@pelzflorian.de> (raw)
In-Reply-To: <8735af9i8b.fsf@nckx> (Tobias Geerinckx-Rice's message of "Sat, 19 Nov 2022 14:37:16 +0100")

Hi Tobias, thanks for your thoughts.

Tobias Geerinckx-Rice <me@tobias.gr> writes:
> pelzflorian (Florian Pelz) 写道:
>> @quotation Note
>> Naturally, no security fixes can be provided for old versions of Guix
>> or its channels.  This also means that careless use of @command{guix
>> time-machine} opens the door to downgrade attacks.
>> @xref{Invoking guix pull, @option{--allow-downgrades}}.
>> @end quotation
> ‘Attack’ is a very big word.  It should not end a paragraph.  What
> would the downgrade attack—distinct from a downgrade—look like?

My choice of words was the same as in the unattended upgrades service,
but perhaps I should add before the @xref:

Suggestions to ``just use the time machine'' could be attempts to trick
people to use old software.  But they can also get you back to a working
state.

Regards,
Florian




  reply	other threads:[~2022-11-19 17:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-19 12:09 [bug#59383] [PATCH] doc: Call out potential for downgrade attacks with time-machine pelzflorian (Florian Pelz)
2022-11-19 13:37 ` Tobias Geerinckx-Rice via Guix-patches via
2022-11-19 17:39   ` pelzflorian (Florian Pelz) [this message]
2022-11-21 11:19     ` zimoun
2022-11-22  7:58       ` Ludovic Courtès
2022-11-22 14:47         ` bug#59383: " pelzflorian (Florian Pelz)

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=87wn7qn8rd.fsf@pelzflorian.de \
    --to=pelzflorian@pelzflorian.de \
    --cc=59383@debbugs.gnu.org \
    --cc=me@tobias.gr \
    /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.