From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: 59383@debbugs.gnu.org
Subject: [bug#59383] [PATCH] doc: Call out potential for downgrade attacks with time-machine.
Date: Sat, 19 Nov 2022 13:09:31 +0100 [thread overview]
Message-ID: <87v8nbjgck.fsf@pelzflorian.de> (raw)
* doc/guix.texi (Invoking guix time-machine): Add a note.
---
doc/guix.texi | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/doc/guix.texi b/doc/guix.texi
index eaecfd0daa..c29db13be6 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -60,7 +60,7 @@
Copyright @copyright{} 2018 Mike Gerwitz@*
Copyright @copyright{} 2018 Pierre-Antoine Rouby@*
Copyright @copyright{} 2018, 2019 Gábor Boskovits@*
-Copyright @copyright{} 2018, 2019, 2020 Florian Pelz@*
+Copyright @copyright{} 2018, 2019, 2020, 2022 Florian Pelz@*
Copyright @copyright{} 2018 Laura Lazzati@*
Copyright @copyright{} 2018 Alex Vong@*
Copyright @copyright{} 2019 Josh Holland@*
@@ -4834,6 +4834,13 @@ Invoking guix time-machine
large number of packages; the result is cached though and subsequent
commands targeting the same commit are almost instantaneous.
+@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
+
The general syntax is:
@example
base-commit: 7502af793172714b2b322c21ba2379c698108ef2
--
2.38.0
next reply other threads:[~2022-11-19 12:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 12:09 pelzflorian (Florian Pelz) [this message]
2022-11-19 13:37 ` [bug#59383] [PATCH] doc: Call out potential for downgrade attacks with time-machine Tobias Geerinckx-Rice via Guix-patches via
2022-11-19 17:39 ` pelzflorian (Florian Pelz)
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=87v8nbjgck.fsf@pelzflorian.de \
--to=pelzflorian@pelzflorian.de \
--cc=59383@debbugs.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.