Eu tenho chaves configuradas para que eu possa fazer login no SVN_HOST assim:
ssh <USER_NAME>@<SVN_HOST>
Vou me registrar no SVN_HOST sem solicitação de senha. Por enquanto, tudo bem; no entanto:
svn update svn+ssh://<USER_NAME>@<SVN_HOST>/<PATH_TO_REPO> <DEST_PATH>
Ainda solicita:
<USER_NAME>@<SVN_HOST>'s password:
Quando eu digito a senha, ela funciona como eu esperava; no entanto, não entendo por que ele insiste em solicitar senha no caso do svn + ssh.
Obrigado antecipadamente.
EDIT: Como solicitado, saída SSH Verbose via:
SVN_SSH="ssh -v " svn update svn+ssh://<USER_NAME>@<SVN_HOST>/<PATH_TO_REPO> <DEST_PATH>
Resultados em:
OpenSSH_5.9p1 Debian-5ubuntu1, OpenSSL 1.0.1 14 Mar 2012
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to <SVN_HOST> [<SVN_HOST>] port 22.
debug1: Connection established.
debug1: permanently_set_uid: 0/0
debug1: identity file /root/.ssh/id_rsa type -1
debug1: identity file /root/.ssh/id_rsa-cert type -1
debug1: identity file /root/.ssh/id_dsa type -1
debug1: identity file /root/.ssh/id_dsa-cert type -1
debug1: identity file /root/.ssh/id_ecdsa type -1
debug1: identity file /root/.ssh/id_ecdsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.1p1 Debian-5ubuntu1
debug1: match: OpenSSH_5.1p1 Debian-5ubuntu1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Server host key: RSA cd:32:17:49:fa:19:aa:64:57:91:76:0d:76:19:82:2f
debug1: Host '<SVN_HOST>' is known and matches the RSA host key.
debug1: Found key in /root/.ssh/known_hosts:1
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Trying private key: /root/.ssh/id_rsa
debug1: Trying private key: /root/.ssh/id_dsa
debug1: Trying private key: /root/.ssh/id_ecdsa
debug1: Next authentication method: password
Em seguida, solicite a senha:
<USER_NAME>@<SVN_HOST>'s password:
Depois de inserir a senha:
debug1: Authentication succeeded (password).
Authenticated to <SVN_HOST> ([<SVN_HOST>]:22).
debug1: channel 0: new [client-session]
debug1: Requesting [email protected]
debug1: Entering interactive session.
debug1: Sending environment.
debug1: Sending env LC_MESSAGES = en_CA.UTF-8
debug1: Sending env LC_COLLATE = en_CA.UTF-8
debug1: Sending env LANG = en_US.UTF-8
debug1: Sending env LC_CTYPE = en_CA.UTF-8
debug1: Sending command: svnserve -t
At revision <REV_NUM>.
Key Gen foi feito assim:
ssh-keygen
Usando padrões, então:
ssh-copy-id -i ~/.ssh/id_rsa.pub <USER_NAME>@<SVN_HOST>
Você gerou a chave como um usuário normal, por isso ela é armazenada em /home/bob/.ssh/ . No entanto, você está executando svn como root em sudo e, portanto, o cliente SSH está procurando chaves em /root/.ssh/ . Você precisa executar svn como usuário normal, copiar a chave para /root/.ssh/ ou configurar ssh para procurar chaves em outro lugar:
sudo SVN_SSH="ssh -i /home/bob/.ssh/id_rsa " svn update ...