r/w developer access not working for me

[Jon Turney]

On 23/09/2026 11:03, Mark Geisert wrote:
> Hi folks, especially jturney,
> I've tried cloning the newlib-cygwin repository using the incantation 
> provided under "Git for developers with read/write access" on
> https://cygwin.com/git.html.  The error report is...

Yeah, that page could probably do with some updating.

>> Cloning into 'newlib-cygwin'...
>> ** WARNING: connection is not using a post-quantum key exchange 
>> algorithm.
>> ** This session may be vulnerable to "store now, decrypt later" attacks.
>> ** The server may need to be upgraded. See https://openssh.com/pq.html
>>
>> FATAL -- ACCESS DENIED
>> Repo            git/newlib-cygwin
>> User            Mark_Geisert
>> Stage           Before git was called
>> Operation       Repo read
>>
>> FATAL: R any git/newlib-cygwin Mark_Geisert DENIED by fallthru
>> (or you mis-spelled the reponame)
>> fatal: Could not read from remote repository.
>>
>> Please make sure you have the correct access rights
>> and the repository exists.
> 
> In my ~/.ssh/config file I have
>> Host cygwin.com
>>     User cygwin
>>     IdentityFile ~/.ssh/id_cygwin

So, you have it all correctly set up for gitolite-moderated access, 
(which uses the shared login 'cygwin').

And that's confirmed by that error message which is coming from gitolite.

Unfortunately, gitolite isn't (currently) set up to permit access to the 
newlib-cygwin repo, so you need to be using your sourceware login.

I've done a bit of updating of that page so it contains a bit more 
information about where gitolite/non-gitolite access is appropriate.

> Changing User from "cygwin" to "Mark_Geisert" throws a different error 
> including the following...
>> Mark_Geisert-rDBXBDvO6BXQT0dZR+AlfA@public.gmane.org: Permission 
>> denied (publickey).
>> fatal: Could not read from remote repository.
> 
> There must be something obvious I'm doing wrong but I've got no idea.
> Thanks for any leads,

The username you are trying there is some internal-to-gitolite detail 
used to identify the owner of the ssh key presented.

You need to use your sourceware login.