From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Permission denied on git.ipfire.org
Date: Mon, 05 Aug 2019 16:19:29 +0100 [thread overview]
Message-ID: <FDD2A1B9-9F77-4B85-9157-245563692BDB@ipfire.org> (raw)
In-Reply-To: <bda6f462-4102-599e-0f4b-be4f7b7c1e89@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1336 bytes --]
Hey,
Yes. I am aware of this and working on it.
The reason is that I (had to?) roll out Kerberos and you guys do not have a Kerberos account, yet.
The module that is meant to be doing this is compiling for the whole day already :(
-Michael
> On 4 Aug 2019, at 13:00, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>
> Hi,
>
> today I tried to lgon to git.ipfire.org after some time.
>
> After updating "/root/.ssh/known_hosts" I still get "Permission denied":
>
> ***SNIP***
> root(a)Devel: /home/matz/ipfire-2.x # git pull origin next
> The authenticity of host 'git.ipfire.org (81.3.27.38)' can't be established.
> ECDSA key fingerprint is SHA256:DjAG8b+d3dQEA9+Lxjmtv0loGqS6eXTv83Faz19hjUs.
> Are you sure you want to continue connecting (yes/no)? yes
> Warning: Permanently added 'git.ipfire.org,81.3.27.38' (ECDSA) to the
> list of known hosts.
> mfischer(a)git.ipfire.org's password:
> Permission denied, please try again.
> mfischer(a)git.ipfire.org's password:
> Permission denied, please try again.
> mfischer(a)git.ipfire.org's password:
> Connection closed by 81.3.27.38 port 22
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
> ***SNAP***
>
> Any hints?
>
> Best,
> Matthias
next prev parent reply other threads:[~2019-08-05 15:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-04 12:00 Matthias Fischer
2019-08-05 15:19 ` Michael Tremer [this message]
2019-08-11 7:56 ` Matthias Fischer
2019-08-14 10:36 ` Michael Tremer
2019-08-14 16:41 ` Matthias Fischer
2019-08-15 15:58 ` Michael Tremer
2019-08-15 16:26 ` Matthias Fischer
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=FDD2A1B9-9F77-4B85-9157-245563692BDB@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