Thread: Access problen with pgpool2 repository

Access problen with pgpool2 repository

From
Tatsuo Ishii
Date:
Hi,

We are using:
ssh://git@git.postgresql.org/pgpool2.git
and yesterday I have added new committer to the repository.
(write access was given to him).

His community account is "kawamoto@sraoss.co.jp".

However when he tries to execute:
ssh://git@git.postgresql.org/pgpool2.git

He gets:
Permission denied (publickey)

He checked his .ssh and public key, it seems they are correct.

Any suggestion?

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp



Re: Access problen with pgpool2 repository

From
"Jonathan S. Katz"
Date:
Hi Tatsuo,

On 5/24/21 9:33 PM, Tatsuo Ishii wrote:
> Hi,
>
> We are using:
> ssh://git@git.postgresql.org/pgpool2.git
> and yesterday I have added new committer to the repository.
> (write access was given to him).
>
> His community account is "kawamoto@sraoss.co.jp".
>
> However when he tries to execute:
> ssh://git@git.postgresql.org/pgpool2.git
>
> He gets:
> Permission denied (publickey)
>
> He checked his .ssh and public key, it seems they are correct.

Is his public key saved to his community user profile?

https://www.postgresql.org/account/profile/

If that does not solve the issue, someone from the pginfra team will
have to investigate further.

Thanks,

Jonathan


Attachment
Hi Jonathan.

Thank you for taking care of this.

> Hi Tatsuo,
> 
> On 5/24/21 9:33 PM, Tatsuo Ishii wrote:
>> Hi,
>> 
>> We are using:
>> ssh://git@git.postgresql.org/pgpool2.git
>> and yesterday I have added new committer to the repository.
>> (write access was given to him).
>> 
>> His community account is "kawamoto@sraoss.co.jp".
>> 
>> However when he tries to execute:
>> ssh://git@git.postgresql.org/pgpool2.git
>> 
>> He gets:
>> Permission denied (publickey)
>> 
>> He checked his .ssh and public key, it seems they are correct.
> 
> Is his public key saved to his community user profile?
> 
> https://www.postgresql.org/account/profile/

Yes.

> If that does not solve the issue, someone from the pginfra team will
> have to investigate further.
> 
> Thanks,
> 
> Jonathan
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp



On Tue, May 25, 2021 at 4:00 AM Tatsuo Ishii <ishii@sraoss.co.jp> wrote:
>
> Hi Jonathan.
>
> Thank you for taking care of this.
>
> > Hi Tatsuo,
> >
> > On 5/24/21 9:33 PM, Tatsuo Ishii wrote:
> >> Hi,
> >>
> >> We are using:
> >> ssh://git@git.postgresql.org/pgpool2.git
> >> and yesterday I have added new committer to the repository.
> >> (write access was given to him).
> >>
> >> His community account is "kawamoto@sraoss.co.jp".
> >>
> >> However when he tries to execute:
> >> ssh://git@git.postgresql.org/pgpool2.git
> >>
> >> He gets:
> >> Permission denied (publickey)
> >>
> >> He checked his .ssh and public key, it seems they are correct.

I see multiple attempts to log in as kawamoto. That would indicate
he's not actually using git@git.postgresql.org in the url. But they
could also be independent attempts -- can you please provide an exact
time when it was attempted, so I can see if I can find more details in
the log?

-- 
 Magnus Hagander
 Me: https://www.hagander.net/
 Work: https://www.redpill-linpro.com/



> On Tue, May 25, 2021 at 4:00 AM Tatsuo Ishii <ishii@sraoss.co.jp> wrote:
>>
>> Hi Jonathan.
>>
>> Thank you for taking care of this.
>>
>> > Hi Tatsuo,
>> >
>> > On 5/24/21 9:33 PM, Tatsuo Ishii wrote:
>> >> Hi,
>> >>
>> >> We are using:
>> >> ssh://git@git.postgresql.org/pgpool2.git
>> >> and yesterday I have added new committer to the repository.
>> >> (write access was given to him).
>> >>
>> >> His community account is "kawamoto@sraoss.co.jp".
>> >>
>> >> However when he tries to execute:
>> >> ssh://git@git.postgresql.org/pgpool2.git
>> >>
>> >> He gets:
>> >> Permission denied (publickey)
>> >>
>> >> He checked his .ssh and public key, it seems they are correct.
> 
> I see multiple attempts to log in as kawamoto. That would indicate
> he's not actually using git@git.postgresql.org in the url. But they
> could also be independent attempts -- can you please provide an exact
> time when it was attempted, so I can see if I can find more details in
> the log?

First he tried:

ssh -T git@git.postgresql.org -vvv

around 11:32:37 JST. The purpose was to get the ssh debug log. He was
trying to find out the cause of the issue (Permission denied).

Next he tried to login as kawamoto because he thought using kawamoto
instead of git might help. That was around:

13:33:58 JST

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp



>> On Tue, May 25, 2021 at 4:00 AM Tatsuo Ishii <ishii@sraoss.co.jp> wrote:
>>>
>>> Hi Jonathan.
>>>
>>> Thank you for taking care of this.
>>>
>>> > Hi Tatsuo,
>>> >
>>> > On 5/24/21 9:33 PM, Tatsuo Ishii wrote:
>>> >> Hi,
>>> >>
>>> >> We are using:
>>> >> ssh://git@git.postgresql.org/pgpool2.git
>>> >> and yesterday I have added new committer to the repository.
>>> >> (write access was given to him).
>>> >>
>>> >> His community account is "kawamoto@sraoss.co.jp".
>>> >>
>>> >> However when he tries to execute:
>>> >> ssh://git@git.postgresql.org/pgpool2.git
>>> >>
>>> >> He gets:
>>> >> Permission denied (publickey)
>>> >>
>>> >> He checked his .ssh and public key, it seems they are correct.
>> 
>> I see multiple attempts to log in as kawamoto. That would indicate
>> he's not actually using git@git.postgresql.org in the url. But they
>> could also be independent attempts -- can you please provide an exact
>> time when it was attempted, so I can see if I can find more details in
>> the log?
> 
> First he tried:
> 
> ssh -T git@git.postgresql.org -vvv
> 
> around 11:32:37 JST. The purpose was to get the ssh debug log. He was
> trying to find out the cause of the issue (Permission denied).
> 
> Next he tried to login as kawamoto because he thought using kawamoto
> instead of git might help. That was around:
> 
> 13:33:58 JST

Note that those time are from slack log while I and Kawamoto made the
conversation in slack. Actual time he ran ssh could be earlier.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp



Hi Magnus,

>>> On Tue, May 25, 2021 at 4:00 AM Tatsuo Ishii <ishii@sraoss.co.jp> wrote:
>>>>
>>>> Hi Jonathan.
>>>>
>>>> Thank you for taking care of this.
>>>>
>>>> > Hi Tatsuo,
>>>> >
>>>> > On 5/24/21 9:33 PM, Tatsuo Ishii wrote:
>>>> >> Hi,
>>>> >>
>>>> >> We are using:
>>>> >> ssh://git@git.postgresql.org/pgpool2.git
>>>> >> and yesterday I have added new committer to the repository.
>>>> >> (write access was given to him).
>>>> >>
>>>> >> His community account is "kawamoto@sraoss.co.jp".
>>>> >>
>>>> >> However when he tries to execute:
>>>> >> ssh://git@git.postgresql.org/pgpool2.git
>>>> >>
>>>> >> He gets:
>>>> >> Permission denied (publickey)
>>>> >>
>>>> >> He checked his .ssh and public key, it seems they are correct.
>>> 
>>> I see multiple attempts to log in as kawamoto. That would indicate
>>> he's not actually using git@git.postgresql.org in the url. But they
>>> could also be independent attempts -- can you please provide an exact
>>> time when it was attempted, so I can see if I can find more details in
>>> the log?
>> 
>> First he tried:
>> 
>> ssh -T git@git.postgresql.org -vvv
>> 
>> around 11:32:37 JST. The purpose was to get the ssh debug log. He was
>> trying to find out the cause of the issue (Permission denied).
>> 
>> Next he tried to login as kawamoto because he thought using kawamoto
>> instead of git might help. That was around:
>> 
>> 13:33:58 JST
> 
> Note that those time are from slack log while I and Kawamoto made the
> conversation in slack. Actual time he ran ssh could be earlier.

- Re-register ssh public key to the organization account (id: kawamoto)
- Change the access right to "Read" and the change the access right back to "Write".

So far none of them helped. Other attempt we do no try yet is,
dropping his repository account from the git management then re-create
it. I am afraid this may loose existing logs and I would like to
confirm we should try it or not. Comment?

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp