public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Permission denied on git.ipfire.org
Date: Wed, 14 Aug 2019 18:41:32 +0200	[thread overview]
Message-ID: <c5087d09-4950-0160-55bf-45a6e9f22edd@ipfire.org> (raw)
In-Reply-To: <220FB358-C500-40E9-AD8E-0677C542C421@ipfire.org>

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

On 14.08.2019 12:36, Michael Tremer wrote:
> Hey,

Hi,

> Sorry for the late reply. This was a bit more stressful than I thought…

No problem - I'm reading this list and know what's going on... ;-)

> However, please log in on https://people.ipfire.org with your usual credentials and change your password.

Done.

> That will create a Kerberos principal for your account which will allow you to log in again.

Sorry, but I did as you wrote, changed password, at first everything
looked ok, but now I get an error again:

Error 429
oops, something went wrong

This happens with the old AND with the new password.

What can I do? Wait?

Best,
Matthias

> Best,
> -Michael
> 
>> On 11 Aug 2019, at 08:56, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>> 
>> HI,
>> 
>> just wanted to ask:
>> 
>> I'm still getting "permission denied":
>> 
>> ***SNIP***
>> root(a)Devel: /home/matz/ipfire-2.x # git checkout next
>> Switched to branch 'next'
>> root(a)Devel: /home/matz/ipfire-2.x # git pull origin next
>> 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**
>> 
>> Anything I can do from my side?
>> 
>> Best,
>> Matthias
>> 
>> On 05.08.2019 17:19, Michael Tremer wrote:
>>> 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
>>> 
>>> 
>> 
> 
> 


  reply	other threads:[~2019-08-14 16:41 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
2019-08-11  7:56   ` Matthias Fischer
2019-08-14 10:36     ` Michael Tremer
2019-08-14 16:41       ` Matthias Fischer [this message]
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=c5087d09-4950-0160-55bf-45a6e9f22edd@ipfire.org \
    --to=matthias.fischer@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