| 1 |
On Mon, Apr 27, 2020 at 7:04 AM Kent Fredric <kentnl@g.o> wrote: |
| 2 |
|
| 3 |
> On Mon, 27 Apr 2020 09:43:44 -0400 |
| 4 |
> Mike Gilbert <floppym@g.o> wrote: |
| 5 |
> |
| 6 |
> > He was replying to me. Your master connection will continue to work |
| 7 |
> > just fine, as I said in my previous message. |
| 8 |
> |
| 9 |
> I must have lost something in grammar, because no matter how many times I |
| 10 |
> read: |
| 11 |
> |
| 12 |
> > If you are authenticating that master connection as the "git" user, I |
| 13 |
> > suspect it will not affect you. If you are using it to push to |
| 14 |
> > gentoo.git, that is almost certainly the case. |
| 15 |
> |
| 16 |
> I interpret that as: |
| 17 |
> |
| 18 |
> - Anonymous fetch is fine |
| 19 |
> - Authorised Push will fail |
| 20 |
> |
| 21 |
|
| 22 |
"If you are authenticating the master connection as the 'git' user then |
| 23 |
this change will not affect you. |
| 24 |
"If you are using controlmaster to push to git.gentoo.org, then you are |
| 25 |
definitely authenticating as user=git because there is no other way to |
| 26 |
commit to ::gentoo." |
| 27 |
|
| 28 |
|
| 29 |
> |
| 30 |
> But I guess my mistake is in that we don't push with "user@git ...", we |
| 31 |
> push with "git@ ... ", and the SSH key is the gate keeper of "push will |
| 32 |
> work", not the UID. |
| 33 |
> |
| 34 |
> Right? |
| 35 |
> |
| 36 |
|
| 37 |
A working ssh key for user=git is a necessary (but not sufficient) |
| 38 |
component of a successful git push. |
| 39 |
|
| 40 |
|
| 41 |
> |
| 42 |
> So assuming you're using git@ for fetch *and* push, *then* it will |
| 43 |
> continue to work. |
| 44 |
> |
| 45 |
> Right? |
| 46 |
> |
| 47 |
|
| 48 |
Correct. |
| 49 |
|
| 50 |
|
| 51 |
> |
| 52 |
> Forgive me for any potential idiocy, language and remembering the |
| 53 |
> details of everything all the time is hard. |
| 54 |
> |
| 55 |
|
| 56 |
I don't actually expect people to know these details. |
Archives