Get assertion error when trying to Login With Public Key

[wjflow]

Hi All, having a bit of a hard time I want to ssh into a server and execute some commands with this:
Login With Public Key

Open Connection  xx.xxx.xx.xxx  port=22
Get Connection    
Login With Public Key     username   /Users/thatsme/.ssh/id_rsa  
Debug
${output}=  Execute Command  ls -al
log to console  ${\n}${output}
Close All Connections

But every time I run it it opens the connection but fails 20190724 15:00:40.573 : FAIL : AssertionError
stumped here big time I can got to my term and ssh username@XX.XX.XX.XX and it works fine any ideas?

[cristii006]

Hello,

I tried to reproduce the problem you described, Linux to Linux and Windows to Linux works well, but I didn't manage to test Linux to Windows login . Could you tell me what you did to obtain this error and provide more details(OS used SSHLibrary version, SSH server that you used, etc.) that can help us reproduce the problem you described?

BR,
Cristi.

[wjflow]

Hi Cristi So to answer your questions: I am going from OSX (Mac) to Centos 7 Using robotframework-sshlibrary 3.3.0 on my remote server I am using: debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4 my code is very simple: *Login With Public Key* *Open Connection* XX.XXX.XX.XXX *Get Connection* *Login With Public Key* USERNAME /Users/my_dir/.ssh/id_rsa ${output}= *Execute Command* ls -al *log to console* ${\n}${output} *Close All Connections* I get Starting test: Test.Tests.One.Login With Public Key 20190729 09:42:48.370 : INFO : index=2 host=XX.XXX.XX.XXX alias=None port=22 timeout=3 seconds newline= prompt=None term_type=vt100 width=80 height=24 path_separator=/ encoding=UTF-8 20190729 09:42:48.371 : INFO : Logging into 'XX.XXX.XX.XXX:22' as 'USERNAME'. 20190729 09:42:48.520 : FAIL : Login with public key failed for user 'USERNAME'. Ending test: Test.Tests.One.Login With Public Key Thanks Bill

…

On Mon, Jul 29, 2019 at 7:06 AM Simandan Andrei-Cristian < ***@***.***> wrote: Hello, I tried to reproduce the problem you described, Linux to Linux and Windows to Linux works well, but I didn't manage to test Linux to Windows login . Could you tell me what you did to obtain this error and provide more details(OS used SSHLibrary version, SSH server that you used, etc.) that can help us reproduce the problem you described? BR, Cristi. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#322?email_source=notifications&email_token=AMWPZKKIPFCYLU4NOBVLKQTQB32P5A5CNFSM4IGVGK32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3A2EVQ#issuecomment-516006486>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AMWPZKO7L3GFGN6TZJMUWMDQB32P5ANCNFSM4IGVGK3Q> .

[wjflow]

Hi all I changed my code to include Enable Ssh Logging and got this

DEB [20190729-12:52:20.931] thr=2 paramiko.transport: Adding ssh-ed25519 host key for xx.xxx.xx.xxx: b'594982e93ccf7586d654dac5a11c5047'
DEB [20190729-12:52:20.985] thr=1 paramiko.transport: userauth is OK
DEB [20190729-12:52:20.993] thr=1 paramiko.transport: Authentication type (password) not permitted.
DEB [20190729-12:52:20.993] thr=1 paramiko.transport: Allowed methods: ['publickey', 'gssapi-keyex', 'gssapi-with-mic']

is it somehow passing a password? So basically it is looking to me that it makes the connection logs on and then bombs out before it executes the command

on my server side I see this:

Jul 29 12:33:16 2401 sshd[22605]: Accepted publickey for forest from xx.x.xx.xxx port 62577
Jul 29 12:39:06 2401 sshd[22670]: Connection closed by xx.xx.xx.xx port 62869 [preauth]
Jul 29 12:40:17 2401 sshd[22708]: Connection closed by xx.xx.xx.xx port 62917 [preauth]

[cristii006]

Hello William,

I managed to reproduce the problem you described in your last comment but it doesn't come from SSHLibrary. I found this issue in Paramiko paramiko/paramiko#1135 but the problem seems to come from OpenSSH. This problem is expected to be fixed in the next months.

BR,
Cristi.

[mika-b]

It seems the issue with newer key format was fixed with paramiko 2.7 released in December 2019. This issue can probably be closed.

http://www.paramiko.org/changelog.html#2.7.0

[cristii006]

Using paramiko 2.7 this problem does not occur anymore. This issue can now be closed.

[santanukumarg09]

I am facing similar issue with
robotframework-sshlibrary version : 3.7.0
paramiko vesrion 2.7.2

but this issue is not there for
robotframework-sshlibrary version : 3.6.0

[mihaiparvu]

@santanukumarg09 can you post the full error message and a simple example that I can reproduce?