Weird Behavior with Certain OpenSSH Keys
Created by: globalcitizen
We observed the case that a certain 4096 bit RSA OpenSSH key that (reportedly: had been and continues to be successfully used with other gitolite based repositories) did not function correctly when used with a new gitlab installation. Other keys work fine with the installation.
After an extensive testing period we determined that the problem was certainly the key in question, which has been in use for a long time and the user does not recall but perhaps was generated some time ago with openssh under cygwin.
The issue observed was that after creating a user and uploading the SSH public key via gitlab, the user cannot read or write to repos to which they are granted access. Deleting and re-creating the user, re-adding rights to various projects from within the gitlab web interface did not help.
The access was tested with: ssh -T git@servername
In all cases, users with other keys created in the same manner at the same time and granted access to the same project were able to see the appropriate R or R W access appear on the appropriate repositories.
The user with the key in question continued to see only the testing repository, always.
Server environment: debian 6.0.5 ("Debian-6+squeeze2") gitolite v2.2.1-5-g8c4d1aa git 1.7.2.5 gitlab 2.9.1 openssh 5.5p1 openssl 0.9.8o