From: Mike Gilbert <floppym@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] [PSA] If you ssh interactively to git.gentoo.org (somehow) let me know.
Date: Mon, 27 Apr 2020 10:46:19 -0400 [thread overview]
Message-ID: <CAJ0EP43QD_4WWWAvNvAVu4ZDOJjkqzOGhXXd+HPJFvQ=YEKjVA@mail.gmail.com> (raw)
In-Reply-To: <20200428020359.3c16e4e5@katipo2.lan>
On Mon, Apr 27, 2020 at 10:03 AM Kent Fredric <kentnl@gentoo.org> wrote:
>
> On Mon, 27 Apr 2020 09:43:44 -0400
> Mike Gilbert <floppym@gentoo.org> wrote:
>
> > He was replying to me. Your master connection will continue to work
> > just fine, as I said in my previous message.
>
> I must have lost something in grammar, because no matter how many times I read:
>
> > If you are authenticating that master connection as the "git" user, I
> > suspect it will not affect you. If you are using it to push to
> > gentoo.git, that is almost certainly the case.
>
> I interpret that as:
>
> - Anonymous fetch is fine
> - Authorised Push will fail
There's no such thing as an "anonymous fetch" from git.gentoo.org. You
must be authenticated to do anything.
> But I guess my mistake is in that we don't push with "user@git ...", we
> push with "git@ ... ", and the SSH key is the gate keeper of "push will
> work", not the UID.
>
> Right?
Correct.
> So assuming you're using git@ for fetch *and* push, *then* it will
> continue to work.
>
> Right?
Correct.
next prev parent reply other threads:[~2020-04-27 14:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-25 21:12 [gentoo-dev] [PSA] If you ssh interactively to git.gentoo.org (somehow) let me know Alec Warner
2020-04-26 12:38 ` Kent Fredric
2020-04-26 18:22 ` Mike Gilbert
2020-04-27 1:00 ` Alec Warner
2020-04-27 13:13 ` Kent Fredric
2020-04-27 13:43 ` Mike Gilbert
2020-04-27 14:03 ` Kent Fredric
2020-04-27 14:46 ` Mike Gilbert [this message]
2020-04-27 17:34 ` Alec Warner
2020-05-22 0:57 ` Alec Warner
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='CAJ0EP43QD_4WWWAvNvAVu4ZDOJjkqzOGhXXd+HPJFvQ=YEKjVA@mail.gmail.com' \
--to=floppym@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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