From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Doing a push to my user git repository
Date: Fri, 11 Jun 2021 12:11:38 +0200 [thread overview]
Message-ID: <fe82a5ed-7a0f-2d39-b9c0-e05feac20b98@ipfire.org> (raw)
In-Reply-To: <ACE2ADB8-7A08-4606-9F0B-D9ACF01259F7@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 4749 bytes --]
Hi Michael,
On 11/06/2021 11:31, Michael Tremer wrote:
> Hello,
>
>> On 10 Jun 2021, at 18:38, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>
>> Hi Michael,
>>
>> On 10/06/2021 14:41, Michael Tremer wrote:
>>> Hello,
>>>> On 10 Jun 2021, at 13:39, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>>>
>>>> Hallo Michael,
>>>>
>>>> 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 using 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 authentication I was able to login with ssh to people.ipfire.org. It immediately logged me out again with the following message:-
>>>>
>>>> fatal: Interactive git shell is not enabled.
>>>> hint: ~/git-shell-commands should exist and have read and execute access.
>>>> Connection to people.ipfire.org closed.
>>>>
>>>> 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 working.
>>> 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 as a remote repository first:
>>> git remote add bonnietwin ssh://bonnietwin(a)people.ipfire.org/…
>>> And then use pull and push :)
>> Struggling to make this work. If I just use ssh://bonnietwin(a)people.ipfire.org/ as above then I get the following message when I try a push.
>>
>> 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=people/bonnietwin/ipfire-2.x.git;a=summary
>
> 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 yesterday.
Anyway it has worked for me today and I have done my first successful push to my repository.
Thanks very much. :-)
>
>> 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 wrong.
>> Looking at my user repository in a browser the url is completely different so I have no idea what I need to use for the url for my repository when accessing it via ssh.
>>
>> I suspect that I have made more than the allowed errors as I now can't even connect any more and get the following message:-
>>
>> ssh: connect to host people.ipfire.org port 22: Network is unreachable
>> fatal: Could not read from remote repository.
>
> LOL. This shouldn’t 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 are authenticated or not.
Shouldn't be a problem in the future because I won't be trying multiple different paths over a short time period. :-)
>
>> Not sure if this will be accessible again after some time or if I am permanently 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 should be able to figure most things out that I will need.
Regards,
Adolf.
>
> -Michael
>
>>
>> Regards,
>>
>> Adolf.
>>> -Michael
>>>>
>>>> Thanks for the help.
>>>>
>>>> Adolf.
>>>>> -Michael
>>>>>> On 10 Jun 2021, at 12:00, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> Sorry for my lack of activities over the last period but I had some non-computing issues to deal with.
>>>>>>
>>>>>> Back again now and starting to look through some previous stuff.
>>>>>>
>>>>>> The user git repository that I have available. Reading through the wiki it looks like I need to use ssh to access it and do a push of any local changes to my user repository.
>>>>>>
>>>>>> I have created an ssh key but the public file will need to be put into the git repository server. Do I just need to send the public key to this distribution list or is there some other process to get it added.
>>>>>>
>>>>>>
>>>>>> Regards,
>>>>>> Adolf.
>>>>
>>>> --
>>>> Sent from my laptop
>
next prev parent reply other threads:[~2021-06-11 10:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 11:00 Adolf Belka
2021-06-10 11:13 ` Michael Tremer
2021-06-10 12:39 ` Adolf Belka
2021-06-10 12:41 ` Michael Tremer
2021-06-10 17:38 ` Adolf Belka
2021-06-11 9:31 ` Michael Tremer
2021-06-11 10:11 ` Adolf Belka [this message]
2021-06-11 10:18 ` Michael Tremer
2021-07-11 12:53 ` Michael Tremer
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=fe82a5ed-7a0f-2d39-b9c0-e05feac20b98@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.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