Gitolite setup getting FATAL: fingerprint failed for '/ tmp / Q3pnE4WVbu'

Question

I am installing gitolite on a CentOS 5.9 server. I created the git user, and then after su - git I managed to get my public key in the ~ / .ssh / directory, I successfully cloned the gitolite repo from github and ran gitolite/install -ln . The next step is to start the setup of the githolite.

 git@hostname [~]# gitolite setup -pk $HOME/.ssh/micha.pub Initialized empty Git repository in /home/git/repositories/gitolite-admin.git/ Initialized empty Git repository in /home/git/repositories/testing.git/ FATAL: fingerprinting failed for '/tmp/Q3pnE4WVbu' 

A google search and a search here on SO did not help me resolve this FATAL error, and now I am fined.

Should I have configured the gitolite.conf file before starting the setup? I followed the instructions at http://gitolite.com/gitolite/progit.html , since they are a little easier than me to understand than the normal documentation of githolite. However, these instructions do not mention setting up the .conf file.

---

UPDATE: I tried to create a new key, and it still doesn't work:

 git@hostname [~]# ssh-keygen -t rsa -C "Gitolite Admin Access (not interactive)" -P "" Generating public/private rsa key pair. Enter file in which to save the key (/home/git/.ssh/id_rsa): /home/git/.ssh/micha /home/git/.ssh/micha already exists. Overwrite (y/n)? y Your identification has been saved in /home/git/.ssh/micha. Your public key has been saved in /home/git/.ssh/micha.pub. The key fingerprint is: 33:b6:62:8b:b9:58:07:7a:71:6a:02:a5:ff:7e:c3:3a Gitolite Admin Access (not interactive) git@hostname [~]# gitolite setup -pk $HOME/.ssh/micha.pub Initialized empty Git repository in /home/git/repositories/gitolite-admin.git/ Initialized empty Git repository in /home/git/repositories/testing.git/ FATAL: fingerprinting failed for '/tmp/pUKqewb66w' 

I also tried replacing $HOME with the full path, just in case su - git messed it up. Are there any problems with my ssh installation? Not sure how it will be when I use ssh to connect to this server.

---

UPDATE: It turns out that the gitolite kept the public keys that I was trying to tune with before this happened. Then I deleted all the repositories, the gitolite source directory, the symlink in ~ / bin and the .gitolite directory and started the installation process again. I cloned a gitolite repo from github, generated a new key after deleting all the other keys that I tried to use before. Then I ran gitolite install -ln and finally

 git@hostname [~]# gitolite setup -pk $HOME/admin.pub Initialized empty Git repository in /home/git/repositories/gitolite-admin.git/ Initialized empty Git repository in /home/git/repositories/testing.git/ FATAL: fingerprinting failed for '/tmp/tsIx4cKWHj' 

Still missing.

Answer 1

As mentioned earlier <, this means that the ssh key was not generated correctly.

Try:

 ssh-keygen -t rsa -f "${H}/.ssh/micha" -C "Gitolite Admin access (not interactive)" -q -P "" 

---

OP mwotton reports that clearing ~ / .ssh of any previous ssh keys was a solution.
This is because the ssh-authkeys.fp_file() function is called with a search :

 chomp( my @pubkeys = `find keydir/ -type f -name "*.pub" | sort` ); 

This way, it can capture previous (possibly damaged) keys that were already in ~/.ssh .

Answer 2

if you take the pub key from puttykeygen, etc., it will be in several lines with headers, for example

 ---- BEGIN SSH2 PUBLIC KEY ---- Comment: " [e-mail] " startofkeylines .... endofkey== ---- END SSH2 PUBLIC KEY ---- 

Remove the start and end lines and Comment: line. Make all key lines in one line. and prefix using ssh-rsa, for example:

 ssh-rsa startofkeylines....endofkey== 

This is what worked for me.

Answer 3

gitolite imprints all the keys in the .ssh directory, including the authorized_keys file. Remove any unnecessary or damaged keys from the .ssh directory and authorized_keys file.

Answer 4

I ran into the same problem. It turned out that during copy-paste I included a new line in one of my keys. Took me a while to notice this ...

Answer 5

You wrote: “It turns out that the gitolite kept public keys, which I tried to configure before this happened.”

I had the same problem. I get an error message:

FATAL: fingerprint failed for 'keydir / jsmith.pub'

I deleted the bad key on the client side and did git push, but still the same question. So I had to connect to the gitolite server and run the following:

 rm ~/.gitolite/keydir/jsmith.pub gitolite setup 

This fixed the problem. This works because of the gitolit documentation: "Pubkey files from this click are uploaded to ~ / .gitolite / keydir". Well, if some FATAL error occurs, then the pub keys will not be placed in the right place. That way, you could even format your ssh keys correctly, and it still won't be written.

Answer 6

I tried all key recovery, gitolite recovery, clearing all key files, etc., all without success, until I started learning the Git story for gitolit.

The problem was that the main branch in the github and google.code repositories was broken. I checked the latest stable version v3.6.4 with a fingerprint issue. I think I can notice a recent commit that guesses this.

Answer 7

For me, I worked with no , working with the gitolite team as the root . I created a git account (and found out that it should be an account that can be registered in ... that is, there is no /bin/false in /etc/passwd ).

Answer 8

I updated the gitolit from v2 to v3, starts the installation and configuration of the administrator key

then forcibly click config repository, all problems are now fixed.

Answer 9

The problem I ran into was that openssh, in or around version v6.8, changed the default cipher for the fingerprint (ssh-keygen -lf path-to-key), so now you need to explicitly pass the encryption type ( -E md5) to get inherited behavior. A look at the CHANGES file shows that v3.6.5 from gitolite "will correctly adjust the ssh fingerprint of the new style (thanks to Robin Johnson)." An update for githolite solved my problem.