[cfarm-users] gcc202: New UltraSparc T5 machine

[Kaz Kylheku]

On 27.07.2017 13:34, Segher Boessenkool wrote:
> On Thu, Jul 27, 2017 at 01:03:18PM -0700, Kaz Kylheku via cfarm-users 
> wrote:
>> On 21.07.2017 13:37, Baptiste Jonglez via cfarm-users wrote:
>> >To access the new machine, "ssh MY_USER_LOGIN at gcc202.fsffrance.org"
>> >should
>> >work for all farm accounts.
>> 
>> Hi Baptiste,
>> 
>> It doesn't.
>> 
>> gcc110 -- good:
>> 
>>   $ ssh gcc110.fsffrance.org
>>   Last login: Sat Jul  1 14:18:27 2017 from 70.79.163.252
>>   [kaz at gcc1-power7 ~]$
>> 
>> gcc202 -- bad:
>> 
>>   $ ssh gcc202.fsffrance.org
>>   kaz at gcc202.fsffrance.org's password:
>> 
>> The ~/.ssh paraphernalia appears not to be propagated to the machine.
> 
> Works fine for me.  It doesn't accept DSA, maybe that is your problem?

debug1: Next authentication method: publickey
debug1: Offering ECDSA public key: /home/kaz/.ssh/id_ecdsa
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey,password
debug1: Offering RSA public key: /home/kaz/.ssh/id_rsa
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey,password
debug1: Offering DSA public key: id_dsa2
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey,password
debug1: Trying private key: /home/kaz/.ssh/id_dsa
debug3: no such identity: /home/kaz/.ssh/id_dsa
debug2: we did not send a packet, disable method
debug3: authmethod_lookup password
debug3: remaining preferred: ,password

That's all the key exchange methods I have, according to the man page 
for ssh-keygen.

I updated the `authorized_keys` on the remote end using another machine 
that I can get into; can I assume it has been synced so that gcc202 sees 
the new keys?

I can't tell from the trace whether a key is being rejected due to not 
being in authorized_keys, or whether it's rejected due to its type.