Operating System - Linux
1754334 Members
2624 Online
108813 Solutions
New Discussion

Unable to Login to iLO4 SSH With RSA-2048 Key

 
SOLVED
Go to solution
Arszilla
Occasional Collector

Unable to Login to iLO4 SSH With RSA-2048 Key

Hi,

I have a HPE ProLiant DL360p Gen 8 server with iLO 4 v2.77. I've authorized my user with my RSA-2048 SSH key, so that I can login without the password and perform basic scripting. However, when I try to SSH into my server, I see the following (with the -vvv flag):

 

debug1: Will attempt key: AWS RSA SHA256:+5f5Eqvw/jXQ+my/bHsSR+X0nFpsaSRT721m3i3HFdw agent
debug1: Will attempt key: Personal (ED25519) ED25519 SHA256:7gwxKgo3cYaY+jdjdbZTsag+jZU53bgxM2mUmRA6/wk agent
debug1: Will attempt key: DigitalOcean ED25519 SHA256:qmWrfFF1FaU4O1uekzeDo8B9TQalb/GU5/8uTsdynTk agent
debug1: Will attempt key: Github ED25519 SHA256:rPoHRwtkr9qynAruiu7KM3X2djzOrHH+B8aiEiSR36w agent
debug1: Will attempt key: Gitlab ED25519 SHA256:6M7QN2ydTC6wyG/soUuv1bkb9I9WEjQRD5OFJA+zdWo agent
debug1: Will attempt key: Personal (RSA) RSA SHA256:rdTu6vslq2hk03JgPwStCjN+aB/Q8pBfnV4rWQsjXAk agent
debug1: Will attempt key: /home/arszilla/.ssh/id_rsa
debug1: Will attempt key: /home/arszilla/.ssh/id_ecdsa
debug1: Will attempt key: /home/arszilla/.ssh/id_ecdsa_sk
debug1: Will attempt key: /home/arszilla/.ssh/id_ed25519
debug1: Will attempt key: /home/arszilla/.ssh/id_ed25519_sk
debug1: Will attempt key: /home/arszilla/.ssh/id_xmss
debug1: Will attempt key: /home/arszilla/.ssh/id_dsa
debug2: pubkey_prepare: done
debug3: send packet: type 5
debug3: receive packet: type 6
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug3: send packet: type 50
debug3: receive packet: type 51
debug1: Authentications that can continue: password,publickey
debug3: start over, passed a different list password,publickey
debug3: preferred gssapi-with-mic,publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Offering public key: AWS RSA SHA256:+5f5Eqvw/jXQ+my/bHsSR+X0nFpsaSRT721m3i3HFdw agent
debug1: send_pubkey_test: no mutual signature algorithm
debug1: Offering public key: Personal (ED25519) ED25519 SHA256:7gwxKgo3cYaY+jdjdbZTsag+jZU53bgxM2mUmRA6/wk agent
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 51
debug1: Authentications that can continue: password,publickey
debug1: Offering public key: DigitalOcean ED25519 SHA256:qmWrfFF1FaU4O1uekzeDo8B9TQalb/GU5/8uTsdynTk agent
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 51
debug1: Authentications that can continue: password,publickey
debug1: Offering public key: Github ED25519 SHA256:rPoHRwtkr9qynAruiu7KM3X2djzOrHH+B8aiEiSR36w agent
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 51
debug1: Authentications that can continue: password,publickey
debug1: Offering public key: Gitlab ED25519 SHA256:6M7QN2ydTC6wyG/soUuv1bkb9I9WEjQRD5OFJA+zdWo agent
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 51
debug1: Authentications that can continue: password,publickey
debug1: Offering public key: Personal (RSA) RSA SHA256:rdTu6vslq2hk03JgPwStCjN+aB/Q8pBfnV4rWQsjXAk agent
debug1: send_pubkey_test: no mutual signature algorithm
debug1: Trying private key: /home/arszilla/.ssh/id_rsa
debug3: no such identity: /home/arszilla/.ssh/id_rsa: No such file or directory
debug1: Trying private key: /home/arszilla/.ssh/id_ecdsa
debug3: no such identity: /home/arszilla/.ssh/id_ecdsa: No such file or directory
debug1: Trying private key: /home/arszilla/.ssh/id_ecdsa_sk
debug3: no such identity: /home/arszilla/.ssh/id_ecdsa_sk: No such file or directory
debug1: Trying private key: /home/arszilla/.ssh/id_ed25519
debug3: no such identity: /home/arszilla/.ssh/id_ed25519: No such file or directory
debug1: Trying private key: /home/arszilla/.ssh/id_ed25519_sk
debug3: no such identity: /home/arszilla/.ssh/id_ed25519_sk: No such file or directory
debug1: Trying private key: /home/arszilla/.ssh/id_xmss
debug3: no such identity: /home/arszilla/.ssh/id_xmss: No such file or directory
debug1: Trying private key: /home/arszilla/.ssh/id_dsa
debug3: no such identity: /home/arszilla/.ssh/id_dsa: No such file or directory
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
root@ilo4.arszilla.network's password:

Here, Personal (RSA) RSA SHA256:rdTu6vslq2hk03JgPwStCjN+aB/Q8pBfnV4rWQsjXAk agent should have been invoked and I should have been able to login. I've tried different RSA keys (as well as a DSA SSH key) on my iLO4.

I cannot seem to be able to login with my SSH key to my iLO and require some assistance on figuring how to fix this.

Any help on solving this would be appreciated.

2 REPLIES 2
ManBha
HPE Pro

Re: Unable to Login to iLO4 SSH With RSA-2048 Key

Hello,

 

Please do log a case using https://support.hpe.com/hpesc/public/home as this might require remote troubleshooting.

 

Thanks.

I work for HPE.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]

Accept or Kudo

Arszilla
Occasional Collector
Solution

Re: Unable to Login to iLO4 SSH With RSA-2048 Key

Apparently, the iLO doesn't like if I use my private key without the device name etc. at the end of the key. i.e.

<key-contents> user@device

 

This fixed my issue for now, but IMO this should not be mandatory, as I use my password manager's SSH sock/agent to authenticate to all my SSH connections.