From: jgart <jgart@dismail.de>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: Feng Shu <tumashu@163.com>,
Thiago Jung Bauermann <bauermann@kolabnow.com>,
help-guix@gnu.org
Subject: Re: was I hacked?
Date: Thu, 14 Apr 2022 16:01:13 -0400 [thread overview]
Message-ID: <20220414160113.GB24691@gac.attlocal.net> (raw)
In-Reply-To: <877d7rveeu.fsf@contorta>
On Thu, 14 Apr 2022 09:05:29 -0700 Vagrant Cascadian <vagrant@debian.org> wrote:
> 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...
That's a very good point that I only just thought of now after doing it ;()
> Is it possible that one of your channels actually had the exact same
> commit in it, but then forked off in different directions?
I don't have any other channel that is mirroring GNU Guix upstream.
> It is rather unsettling to not know what happened...
Yes, it is. I agree.
Others have reported this issue on irc at #guix.
See the logs.
I think they just blindly used --allow-downgrades while I blindly rolled back and forward
Hopefully we find out what happened.
all best,
jgart
next prev parent reply other threads:[~2022-04-14 20:01 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
2022-04-14 20:01 ` jgart [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220414160113.GB24691@gac.attlocal.net \
--to=jgart@dismail.de \
--cc=bauermann@kolabnow.com \
--cc=help-guix@gnu.org \
--cc=tumashu@163.com \
--cc=vagrant@debian.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.