From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Doing a push to my user git repository Date: Sun, 11 Jul 2021 13:53:38 +0100 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3552958013731459670==" List-Id: --===============3552958013731459670== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, I just ran into this again when using non-Kerberos authentication from a diff= erent host (a build server). This is very annoying and I had to several times unblock myself. @Peter: Could you please have a look at this again. -Michael > On 11 Jun 2021, at 11:18, Michael Tremer wrot= e: >=20 > Hello, >=20 >> On 11 Jun 2021, at 11:11, Adolf Belka wrote: >>=20 >> Hi Michael, >>=20 >> On 11/06/2021 11:31, Michael Tremer wrote: >>> Hello, >>>> On 10 Jun 2021, at 18:38, Adolf Belka wrote: >>>>=20 >>>> Hi Michael, >>>>=20 >>>> On 10/06/2021 14:41, Michael Tremer wrote: >>>>> Hello, >>>>>> On 10 Jun 2021, at 13:39, Adolf Belka wrote: >>>>>>=20 >>>>>> Hallo Michael, >>>>>>=20 >>>>>> On 10/06/2021 13:13, Michael Tremer wrote: >>>>>>> Hello Adolf, >>>>>>> We do not use SSH keys in our infrastructure. Instead we use Kerberos= authentication. >>>>>>> For that, you do not have to do anything apart from authenticating us= ing a password as usual. In the background the server will acquire a Kerberos= ticket automatically. >>>>>>> You should be able to log in at people.ipfire.org using SSH with your= username and your password. Can you check if that works? >>>>>> After adding a Match Host command to my ssh_config to allow password a= uthentication I was able to login with ssh to people.ipfire.org. It immediate= ly logged me out again with the following message:- >>>>>>=20 >>>>>> fatal: Interactive git shell is not enabled. >>>>>> hint: ~/git-shell-commands should exist and have read and execute acce= ss. >>>>>> Connection to people.ipfire.org closed. >>>>>>=20 >>>>>> Reading about this I suspect that is expected because I should not be = working with git interactively but it proves that my ssh connection is workin= g. >>>>> Yes, this is correct. This was just to test the SSH connection. >>>>>> I will now try out accessing my user repository via ssh and seeing if = that works. >>>>> You should be able to push things to this repository by setting it up a= s a remote repository first: >>>>> git remote add bonnietwin ssh://bonnietwin(a)people.ipfire.org/=E2=80= =A6 >>>>> And then use pull and push :) >>>> Struggling to make this work. If I just use ssh://bonnietwin(a)people.ip= fire.org/ as above then I get the following message when I try a push. >>>>=20 >>>> fatal: '/' does not appear to be a git repository >>>> fatal: Could not read from remote repository. >>> The full path is on the gitweb page here: https://git.ipfire.org/?p=3Dpeo= ple/bonnietwin/ipfire-2.x.git;a=3Dsummary >>> ssh://bonnietwin(a)people.ipfire.org/pub/git/people/bonnietwin/ipfire-2.= x.git >> That seems so obvious today when you show it but I failed to see it yester= day. >> Anyway it has worked for me today and I have done my first successful push= to my repository. >> Thanks very much. :-) >=20 > Yay \o/ >=20 >>>> I tried adding bonnietwin/ipfire-2.x.git/ to the end of the url but that= gave the same error message.Basically just a guess on my part but it was wro= ng. >>>> Looking at my user repository in a browser the url is completely differe= nt so I have no idea what I need to use for the url for my repository when ac= cessing it via ssh. >>>>=20 >>>> I suspect that I have made more than the allowed errors as I now can't e= ven connect any more and get the following message:- >>>>=20 >>>> ssh: connect to host people.ipfire.org port 22: Network is unreachable >>>> fatal: Could not read from remote repository. >>> LOL. This shouldn=E2=80=99t happen if you authenticate properly. If this = locks you out again send a note to Peter to have a look at this. >> I suspect Fail2Ban just looks at the frequency of attempts whether they ar= e authenticated or not. >> Shouldn't be a problem in the future because I won't be trying multiple di= fferent paths over a short time period. :-) >=20 > Yes, but it seems to count unsupported authentication methods as a failed a= ttempt. But hey, at least it works for now... >=20 >>>> Not sure if this will be accessible again after some time or if I am per= manently blocked and need it to be released. >>> It is a temporary block and should be working again now. >>>> Either way I need and would appreciate some guidance. >>> If you need anything else, just let me know. >> Thanks very much for the help. That has got me going and hopefully I shoul= d be able to figure most things out that I will need. >=20 > :) >=20 > -Michael >=20 >>=20 >> Regards, >> Adolf. >>> -Michael >>>>=20 >>>> Regards, >>>>=20 >>>> Adolf. >>>>> -Michael >>>>>>=20 >>>>>> Thanks for the help. >>>>>>=20 >>>>>> Adolf. >>>>>>> -Michael >>>>>>>> On 10 Jun 2021, at 12:00, Adolf Belka wro= te: >>>>>>>>=20 >>>>>>>> Hi All, >>>>>>>>=20 >>>>>>>> Sorry for my lack of activities over the last period but I had some = non-computing issues to deal with. >>>>>>>>=20 >>>>>>>> Back again now and starting to look through some previous stuff. >>>>>>>>=20 >>>>>>>> The user git repository that I have available. Reading through the w= iki it looks like I need to use ssh to access it and do a push of any local c= hanges to my user repository. >>>>>>>>=20 >>>>>>>> I have created an ssh key but the public file will need to be put in= to the git repository server. Do I just need to send the public key to this d= istribution list or is there some other process to get it added. >>>>>>>>=20 >>>>>>>>=20 >>>>>>>> Regards, >>>>>>>> Adolf. >>>>>>=20 >>>>>> --=20 >>>>>> Sent from my laptop --===============3552958013731459670==--