unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Edouard Klein <edou@rdklein.fr>
To: help-guix@gnu.org
Subject: Re: was I hacked?
Date: Fri, 22 Apr 2022 18:47:37 +0200	[thread overview]
Message-ID: <87r15poybi.fsf@rdklein.fr> (raw)
In-Reply-To: <87ilrab2f7.fsf@dustycloud.org>

Hi,

I diffed the git log of both https://git.sr.ht/~whereiseveryone/pjmkglp
and guix official repo and could not find any difference (apart from the
most recent commits on the official repo of course). I also confirmed,
as had already been said, that commit 950f3e4f98 is indeed a descendant
of 42679e3f81, so the error message makes no sense :/

I have absolutely no idea what went wrong. I'm still very much
interested in the answer, but I've reached the edge of my ability to
investigate.

Let's hope that somebody can find out what went wrong.

Cheers,

Edouard.

Christine Lemmer-Webber <cwebber@dustycloud.org> writes:

> Well good news, jgart pushed them elsewhere in the thread:
>
> jgart <jgart@dismail.de> writes:
>
>> Here are the repos of interest:
>>
>> https://git.sr.ht/~whereiseveryone/pjmkglp
>>
>> https://git.sr.ht/~whereiseveryone/authentification-channels
>>
>> wdyt?
>
>
> Edouard Klein <edou@rdklein.fr> writes:
>
>> Hi,
>>
>> Sorry about the noise, but I'm curious about this as well, and I think
>> if this is indeed an attack that it would be brilliant to see that guix
>> protected against it. I would like to document it.
>>
>> @jgart I can open a git repo for you and lend a hand if you need help
>> pushing the strange branch somewhere.
>>
>> Cheers,
>>
>> Edouard
>>
>> Jack Hill <jackhill@jackhill.us> writes:
>>
>>> On Thu, 14 Apr 2022, jgart wrote:
>>>
>>>> What I not sure of is what path on my system to find the suspicious
>>>> branch/git repo pulled down by `git/guix pull` so I can push it somewhere.
>>>>
>>>> In other words, where does `guix pull` clone the git repo to?
>>>
>>> ~/.cache/guix/checkouts
>>>
>>> ~/.cache/guix/authentication may be interesting as well.
>>>
>>> (I bet (hope?) it's actually XDG_CACHE_DIR/guix but you get the idea)
>>>
>>> Sorry I don't have insight in to what went wrong.
>>>
>>> Take care,
>>> Jack


  reply	other threads:[~2022-04-22 16:56 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
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 [this message]
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=87r15poybi.fsf@rdklein.fr \
    --to=edou@rdklein.fr \
    --cc=help-guix@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.
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).