From: Vagrant Cascadian <vagrant@debian.org>
To: jgart <jgart@dismail.de>, Feng Shu <tumashu@163.com>
Cc: help-guix@gnu.org
Subject: Re: was I hacked?
Date: Thu, 14 Apr 2022 09:05:29 -0700 [thread overview]
Message-ID: <877d7rveeu.fsf@contorta> (raw)
In-Reply-To: <20220414011701.GB3320@gac.attlocal.net>
[-- Attachment #1: Type: text/plain, Size: 2020 bytes --]
On 2022-04-14, jgart wrote:
> On Thu, 14 Apr 2022 08:26:39 +0800 Feng Shu <tumashu@163.com> wrote:
>> jgart <jgart@dismail.de> writes:
>>
>> > On Wed, 13 Apr 2022 02:25:11 -0300 Thiago Jung Bauermann <bauermann@kolabnow.com> wrote:
>> >> I don't understand why Guix thinks that. IIUC 950f3e… is a direct
>> >> descendant of 42679e…
>> >
>> > As of today now the has changed:
>> >
>> > ```
>> > λ guix pull
>> > Updating channel 'guixrus' from Git repository at 'https://git.sr.ht/~whereiseveryone/guixrus'...Updating channel 'nonguix' from Git repository at 'https://gitlab.com/nonguix/nonguix'...Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'...guix pull: error: aborting update of channel 'guix' to commit 5743d505834a8b13778da2c969ea4e15bb7a3a75, which is not a descendant of 42679e3f81a0fa61e225b1f6aa0e80e39625372f
>> > hint: This could indicate that the channel has been tampered with and is trying to force a roll-back, preventing you from getting the latest
>> > updates. If you think this is not the case, explicitly allow non-forward updates.
>> > ```
>> >
>> > I haven't allowed downgrades yet.
>> >
>> > Waiting to see if I get an answer first on why it's happening.
>>
>> Why not roll-back to an older guix, then try guix pull again?
>
> Hi Feng,
>
> Thanks! that worked!!!
>
> I rolled back one generation and ran `guix pull`.
That still does leave me wonder what the deal was...
Was the repository tampered with?
Rolling back to an older generation and then moving forward basically
would be a successfull (hopefully just accidental) attack changing the
commit history! Rolling back to an older generation isn't much different
than just blindly allowing to move forward to a different branch...
Is it possible that one of your channels actually had the exact same
commit in it, but then forked off in different directions?
It is rather unsettling to not know what happened...
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2022-04-14 16:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 1:28 was I hacked? jgart
2022-04-13 5:25 ` Thiago Jung Bauermann
2022-04-13 21:41 ` jgart
2022-04-14 0:26 ` Feng Shu
2022-04-14 5:17 ` jgart
2022-04-14 16:05 ` Vagrant Cascadian [this message]
2022-04-14 20:01 ` jgart
2022-04-14 20:20 ` Christine Lemmer-Webber
2022-04-14 20:27 ` jgart
2022-04-15 1:11 ` Christine Lemmer-Webber
2022-04-15 3:08 ` jgart
2022-04-15 3:31 ` Jack Hill
2022-04-15 14:05 ` jgart
2022-04-15 17:31 ` jgart
2022-04-15 19:43 ` Edouard Klein
2022-04-15 18:56 ` Christine Lemmer-Webber
2022-04-22 16:47 ` Edouard Klein
2022-04-22 19:58 ` Thiago Jung Bauermann
2022-04-23 15:56 ` Dr. Arne Babenhauserheide
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=877d7rveeu.fsf@contorta \
--to=vagrant@debian.org \
--cc=help-guix@gnu.org \
--cc=jgart@dismail.de \
--cc=tumashu@163.com \
/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).