A test against a Linux system could help testing. If you transferred the keypair, it could be possible, that the transfer was not done correctly. On the Windows server - is the public key generated separately for this user/server? Or did you transfer the keypair from a Windows workstation? I'd rather guess, that it is sending the wrong key!ĭo you have a Linux system at hand? That should allow you to check if the same key works from both windows platforms, or if it fails. So I don't really believe, that under 2016 a 'different type of private key' would be sent to the remote host. IPv4 or IPv6 address of the remote machine.A public key is a public key, no matter what OS is connecting to a remote server. You can specify a username and password only, public key only, or both username and password and public key. Only RSA authentication is used.Ĭonfigures the authentication method for the management user. Hmac-sha1 hmac-sha1-96 | hmac-sha1-96 hmac-sha1ĭisables HMAC-SHA1 and HMAC-SHA1-96 authentication for SSH.ĭisables DSA authentication for SSH. Starting from ArubaOS 8.6.0.5, ssh disable-mac hmac-sha1-96 command disables HMAC-SHA1-96 authentication and enables HMAC-SHA1 and HMAC-SHA2-256 authentication.

Starting from ArubaOS 8.6.0.5, the ssh disable-mac hmac-sha1 command disables HMAC-SHA1 authentication and enables HMAC-SHA1-96 and HMAC-SHA2-256 authenticationĭisables HMAC-SHA1-96 authentication for SSH.

This parameter enables the aes-cbc encryption.ĭisables key exchange algorithm for SSH authentication.ĭisables Message Authentication Code algorithm for SSH authentication.ĭisables HMAC-SHA1 authentication for SSH. This parameter enables the aes-ctr encryption.ĭisables AES-CTR authentication for SSH. Specify the cipher to be disabled.ĭisables AES-CBC authentication for SSH. The hmac-sha2-256 parameter can not be disabled.ĭisables cipher authentication for SSH. The SSH authentication supports hmac-sha1, hmac-sha1-96, and hmac-sha2-256 by default. If you specify public-key authentication, you need to load the client X.509 certificate into Mobility Conductor and configure certificate authentication for the management user with the mgmt-user ssh-pubkey command. Public key authentication is supported using a X.509 certificate issued to the management client. This command configures SSH access to a Mobility Conductor.

Windows terminal ssh no kex alg