From: jgart <jgart@dismail.de>
To: Jack Hill <jackhill@jackhill.us>
Cc: Christine Lemmer-Webber <cwebber@dustycloud.org>,
Vagrant Cascadian <vagrant@debian.org>,
Feng Shu <tumashu@163.com>,
Thiago Jung Bauermann <bauermann@kolabnow.com>,
help-guix@gnu.org
Subject: Re: was I hacked?
Date: Fri, 15 Apr 2022 13:31:16 -0400 [thread overview]
Message-ID: <20220415133116.GB31182@gac.attlocal.net> (raw)
In-Reply-To: <20220415100509.GD18482@gac.attlocal.net>
On Fri, 15 Apr 2022 10:05:09 -0400 jgart <jgart@dismail.de> wrote:
> On Thu, 14 Apr 2022 23:31:14 -0400 Jack Hill <jackhill@jackhill.us> wrote:
> > 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.
>
> Hi Jack,
>
> Thank you!
>
> I'll push it soon.
Here are the repos of interest:
https://git.sr.ht/~whereiseveryone/pjmkglp
https://git.sr.ht/~whereiseveryone/authentification-channels
wdyt?
next prev parent reply other threads:[~2022-04-15 17:31 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 [this message]
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=20220415133116.GB31182@gac.attlocal.net \
--to=jgart@dismail.de \
--cc=bauermann@kolabnow.com \
--cc=cwebber@dustycloud.org \
--cc=help-guix@gnu.org \
--cc=jackhill@jackhill.us \
--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.
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).