Unable to connect with public key ed25519 format

[toot...@gmail.com]

Hi list,

I can' t connect to server using ed25519 key format, verbose output being

 debug1: Next authentication method: publickey

debug1: Trying private key: /home/chronos/user/.ssh/id_rsa

debug3: no such identity: /home/chronos/user/.ssh/id_rsa: No such file or directory

debug1: Trying private key: /home/chronos/user/.ssh/id_dsa

debug3: no such identity: /home/chronos/user/.ssh/id_dsa: No such file or directory

debug1: Trying private key: /home/chronos/user/.ssh/id_ecdsa

debug3: no such identity: /home/chronos/user/.ssh/id_ecdsa: No such file or directory

debug1: Offering ED25519 public key: /home/chronos/user/.ssh/id_ed25519

debug3: send_pubkey_test

debug3: send packet: type 50

debug2: we sent a publickey packet, wait for reply

debug3: receive packet: type 51

debug1: Authentications that can continue: publickey,password

debug2: we did not send a packet, disable method

debug3: authmethod_lookup password

debug3: remaining preferred: ,password

debug3: authmethod_is_enabled password

debug1: Next authentication method: password

Server is Debian Stretch but the same happend with Ubuntu 16.04

Another question: I tried to import key like given in faq. Import was successfull but I was unable to connect using the keys. Now I want to remove the identity key I import, how can I do? Both methods given in FAQ doesn' t work (I empty the .ssh directory and the javascript console give error concerning term_.xxx unknown).

Thanks for your support

Daniel 

[toot...@gmail.com]

Got it, bad user connection. Now question is, why I can connect with ssh using shell but not with nassh? From where is nassh reading identity keys? Is nassh connecting using the chrome user or use it effectively the user given in parameter connection?

[TOOTAi H]

Nobody on this ?

--

Daniel Huhardeaux
TOOTAi Networks

[Mike Frysinger]

by design, Secure Shell has no access to your filesystem, so the paths to /home/ will never work. I'm guessing you added custom ssh command line options to do that, so maybe don't?

when you import keys, Secure Shell should be able to find them automatically.

-mike

--
You received this message because you are subscribed to the Google Groups "chromium-hterm" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/6d17b664-3cb9-4fe4-babf-ebc075843f52%40chromium.org.