so using ssh.net library stuff .net application trigger stuff on remote mac os device. after changed user's password managed break functionality somehow , system.log shows me following message:
warning: no suitable primes in /etc/ssh/primes the library gives me message:
an exception of type 'renci.sshnet.common.sshauthenticationexception' occurred in renci.sshnet.dll not handled in user code additional information: no suitable authentication method found complete authentication. sshd debug gives me message:
debug1: server not fork when running in debugging mode. debug1: rexec start in 6 out 6 newsock 6 pipe -1 sock 9 debug1: inetd sockets after dupping: 5, 5 connection 172.16.115.19 port 44670 on 192.168.202.110 port 2222 debug1: client protocol version 2.0; client software version renci.sshnet.sshclient.0.0.1 debug1: no match: renci.sshnet.sshclient.0.0.1 debug1: enabling compatibility mode protocol 2.0 debug1: local version string ssh-2.0-openssh_6.9 debug2: fd 5 setting o_nonblock debug2: network child on pid 569 debug1: list_hostkey_types: [preauth] no supported key exchange algorithms [preauth] debug1: do_cleanup [preauth] debug1: monitor_read_log: child log fd closed debug1: do_cleanup debug1: killing privsep child 569 debug1: audit_event: unhandled event 12 i guessing has keys have changed after password changed, not 100% sure here.
i guessing has keys have changed after password changed, not 100% sure here.
no.
no supported key exchange algorithms [preauth] talks key exchange algorithms. log not complete (-ddd tell more) , older version not verbose in level. can guess server not support anymore method offered ssh.net library.
i go upgrading library in first place. second possibility allow legacy kex algorithms on server, such as:
kexalgorithms curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1,diffie-hellman-group-exchange-sha1
in sshd_config (basically adding diffie-hellman-group1-sha1 , diffie-hellman-group-exchange-sha1 not considered safe these days!).
Comments
Post a Comment