From: Edouard Klein <edou@rdklein.fr>
To: help-guix@gnu.org
Subject: Re: was I hacked?
Date: Fri, 15 Apr 2022 21:43:18 +0200 [thread overview]
Message-ID: <87pmliqgi5.fsf@rdklein.fr> (raw)
In-Reply-To: <alpine.DEB.2.21.2204142328590.11587@marsh.hcoop.net>
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
next prev parent reply other threads:[~2022-04-15 17:44 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 [this message]
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=87pmliqgi5.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.
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.