From c8b1d8cc5b7099d6f150ef2e1f1dc7f92cb65c6c Mon Sep 17 00:00:00 2001 From: Jan Koprowski Date: Sun, 16 Jan 2011 13:43:45 +0100 Subject: [PATCH] Document handling non-openssh but ssh2-compatible public keys by gitolite. --- doc/ssh-troubleshooting.mkd | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/doc/ssh-troubleshooting.mkd b/doc/ssh-troubleshooting.mkd index 0fa7169..8dcc6d9 100644 --- a/doc/ssh-troubleshooting.mkd +++ b/doc/ssh-troubleshooting.mkd @@ -8,6 +8,7 @@ In this document: * (sidebar) why two keys on client for the admin * bypassing gitolite without intending to * basic ssh troubleshooting for the admin + * problems with using non-openssh public keys * windows issues * details * files on the server @@ -320,6 +321,21 @@ from scratch: That's a long sequence but it should work. + + +### problems with using non-openssh public keys + +Gitolite accepts public keys only in openssh format. Trying to use an "ssh2" +key (used by proprietary SSH software) results in: + + WARNING: a pubkey file can only have one line (key); ignoring YourName.pub + +To convert ssh2-compatible keys to openssh run: + + ssh-keygen -i -f /tmp/ssh2/YourName.pub > /tmp/openssh/YourName.pub + +then use the resulting pubkey as you normally would in gitolite. + ### windows issues