public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Doing a push to my user git repository
Date: Thu, 10 Jun 2021 13:41:51 +0100	[thread overview]
Message-ID: <F98B9DE4-7637-401E-BF44-19DF50CD329D@ipfire.org> (raw)
In-Reply-To: <80b1b5d7-71a7-a1e7-fb44-87e4b3a3e171@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2297 bytes --]

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 :)

-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


  reply	other threads:[~2021-06-10 12:41 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 [this message]
2021-06-10 17:38       ` Adolf Belka
2021-06-11  9:31         ` Michael Tremer
2021-06-11 10:11           ` Adolf Belka
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=F98B9DE4-7637-401E-BF44-19DF50CD329D@ipfire.org \
    --to=michael.tremer@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