From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
Cc: | pgsql-www(at)postgresql(dot)org |
Subject: | Re: SSH connection problem (and a typo) |
Date: | 2021-08-27 07:39:49 |
Message-ID: | 2BF18CAC-5341-4F31-8EEC-AEDAB3B7C5DC@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
> On 27 Aug 2021, at 09:37, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> wrote:
>
> At Fri, 27 Aug 2021 09:13:29 +0200, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote in
>>> On 27 Aug 2021, at 04:31, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> wrote:
>>
>>> Is there anything I can check or do to overcome this situation?
>>
>> I don’t think there is. Quoting Magnus from your thread on -hackers:
>>
>> "ssh based access only works for repositories where you have explicit
>> permissions, it does not support anonymous access -- that has to be over
>> https (recommended) or git.
>>
>> And specifically, the postgresql.git repo mirror only allows anonymous
>> access."
>>
>> So the way I read it is that there is nothing wrong with your setup, but the
>> repository you are attempting to clone does not allow setting the access
>> control needed for it to work. postgresql.git only allows http or git, ssh
>> isn’t allowed as it only allows anonymous access.
>
> Ok. Thanks for clarification. I thought that ssh reading access to
> git.postgresql.org is allowed to all who have a community account.
It is, but only for repositories where you have explicitly been granted read
access, it’s not on by default for all repositories.
> So if I fail to access an repository that I suppose I have an access,
> I understand that that means that I should ask the owner of the
> repository.
Correct.
--
Daniel Gustafsson https://vmware.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2021-08-28 14:51:59 | Re: SSH connection problem (and a typo) |
Previous Message | Kyotaro Horiguchi | 2021-08-27 07:37:19 | Re: SSH connection problem (and a typo) |