It is now working for me! Not sure what happened.

Eviatar

On Thursday, 30 June 2016 23:34:49 UTC-7, Dima Pasechnik wrote:
>
> perhaps adding an invalid ssh key still breaks the communication between 
> git server and trac...
> Can they still push changes to the git server? 
>
> On Friday, July 1, 2016 at 12:35:55 AM UTC+1, Viviane Pons wrote:
>>
>> Hi,
>>
>> I'm with two new sage git users: eviatarbach and avenrias and they seem 
>> to have a similar problem. They have put their ssh key on trac (I've 
>> checked), but it keeps saying "Permission denied (publickey)" when they try
>>
>> ssh -T g...@trac.sagemath.org info
>>
>> Here is what they get:
>>
>> OpenSSH_7.2p2 Ubuntu-4ubuntu1, OpenSSL 1.0.2g-fips  1 Mar 2016
>> debug1: Reading configuration data /etc/ssh/ssh_config
>> debug1: /etc/ssh/ssh_config line 19: Applying options for *
>> debug1: Connecting to trac.sagemath.org [104.197.143.230] port 22.
>> debug1: Connection established.
>> debug1: identity file /home/eviatar/.ssh/id_rsa type 1
>> debug1: key_load_public: No such file or directory
>> debug1: identity file /home/eviatar/.ssh/id_rsa-cert type -1
>> debug1: key_load_public: No such file or directory
>> debug1: identity file /home/eviatar/.ssh/id_dsa type -1
>> debug1: key_load_public: No such file or directory
>> debug1: identity file /home/eviatar/.ssh/id_dsa-cert type -1
>> debug1: key_load_public: No such file or directory
>> debug1: identity file /home/eviatar/.ssh/id_ecdsa type -1
>> debug1: key_load_public: No such file or directory
>> debug1: identity file /home/eviatar/.ssh/id_ecdsa-cert type -1
>> debug1: key_load_public: No such file or directory
>> debug1: identity file /home/eviatar/.ssh/id_ed25519 type -1
>> debug1: key_load_public: No such file or directory
>> debug1: identity file /home/eviatar/.ssh/id_ed25519-cert type -1
>> debug1: Enabling compatibility mode for protocol 2.0
>> debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu1
>> debug1: Remote protocol version 2.0, remote software version 
>> OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.7
>> debug1: match: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.7 pat OpenSSH_6.6.1* 
>> compat 0x04000000
>> debug1: Authenticating to trac.sagemath.org:22 as 'git'
>> debug1: SSH2_MSG_KEXINIT sent
>> debug1: SSH2_MSG_KEXINIT received
>> debug1: kex: algorithm: curve255...@libssh.org
>> debug1: kex: host key algorithm: ecdsa-sha2-nistp256
>> debug1: kex: server->client cipher: chacha20...@openssh.com MAC: 
>> <implicit> compression: none
>> debug1: kex: client->server cipher: chacha20...@openssh.com MAC: 
>> <implicit> compression: none
>> debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
>> debug1: Server host key: ecdsa-sha2-nistp256 
>> SHA256:PLGYHWgGgFuDw+Xqa8TSHaJ9AZlcXIiaYUdlrNN1sFU
>> debug1: Host 'trac.sagemath.org' is known and matches the ECDSA host key.
>> debug1: Found key in /home/eviatar/.ssh/known_hosts:2
>> debug1: rekey after 134217728 blocks
>> debug1: SSH2_MSG_NEWKEYS sent
>> debug1: expecting SSH2_MSG_NEWKEYS
>> debug1: rekey after 134217728 blocks
>> debug1: SSH2_MSG_NEWKEYS received
>> debug1: SSH2_MSG_SERVICE_ACCEPT received
>> debug1: Authentications that can continue: publickey
>> debug1: Next authentication method: publickey
>> debug1: Offering RSA public key: /home/eviatar/.ssh/id_rsa
>> debug1: Authentications that can continue: publickey
>> debug1: Trying private key: /home/eviatar/.ssh/id_dsa
>> debug1: Trying private key: /home/eviatar/.ssh/id_ecdsa
>> debug1: Trying private key: /home/eviatar/.ssh/id_ed25519
>> debug1: No more authentication methods to try.
>>
>>  
>>
>> 2016-06-29 3:56 GMT-07:00 tara fife <fi....@gmail.com>:
>>
>>> Thanks everyone, I am able to push changes to trac now.
>>>
>>> Tara
>>>
>>> --
>>> You received this message because you are subscribed to the Google 
>>> Groups "sage-devel" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to sage-devel+...@googlegroups.com.
>>> To post to this group, send email to sage-...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/sage-devel.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to