Using paramiko in python with the latest openssh stable causes: ERR [20141210-00:10:40.363] thr=1 paramiko.transport: Exception: Incompatible ssh peer (no acceptable kex algorithm) ERR [20141210-00:10:40.363] thr=1 paramiko.transport: Traceback (most recent call last): ERR [20141210-00:10:40.363] thr=1 paramiko.transport: File "/usr/lib64/python2.7/site-packages/paramiko/transport.py", line 1448, in run ERR [20141210-00:10:40.363] thr=1 paramiko.transport: self._handler_table[ptype](self, m) ERR [20141210-00:10:40.363] thr=1 paramiko.transport: File "/usr/lib64/python2.7/site-packages/paramiko/transport.py", line 1528, in _negotiate_keys ERR [20141210-00:10:40.364] thr=1 paramiko.transport: self._parse_kex_init(m) ERR [20141210-00:10:40.364] thr=1 paramiko.transport: File "/usr/lib64/python2.7/site-packages/paramiko/transport.py", line 1643, in _parse_kex_init ERR [20141210-00:10:40.364] thr=1 paramiko.transport: raise SSHException('Incompatible ssh peer (no acceptable kex algorithm)') ERR [20141210-00:10:40.364] thr=1 paramiko.transport: SSHException: Incompatible ssh peer (no acceptable kex algorithm) ERR [20141210-00:10:40.364] thr=1 paramiko.transport: Reproducible: Always Steps to Reproduce: 1. install paramiko/openssh 2. try to make a ssh connection 3. Actual Results: fails to connect: Incompatible ssh peer (no acceptable kex algorithm) Expected Results: it should connect properly paramiko >1.15 is known to work with openssh-6.7_p1 I fixed this by keywording: ~dev-python/paramiko-1.15.1 ~dev-python/ecdsa-0.11
paramiko >1.15 is known to work with openssh-6.7_p1 I fixed this by keywording: ~dev-python/paramiko-1.15.1 ~dev-python/ecdsa-0.11 Please expand on this. 1. net-misc/openssh/openssh-6.7_p1-r3.ebuild currently does NOT dep on paramiko at all. Are you suggesting it be made to do so? 2. net-misc/openssh/openssh-6.7_p1-r3.ebuild currently does inherit eutils user flag-o-matic multilib autotools pam systemd versionator missing any python eclass. Where does paramiko get pulled in??? This bug raises more questions than its current input answers. It also seems to me that it warrants assignment to <herd>base-system</herd> and >robbat2@gentoo.org We need a clear indication where python herd is involved here
Paramiko doesn't get pulled in at all, I'm using it as an import in my python code to handle ssh connections.... so I emerge python, I emerge paramiko (both stable) and I get a non working setup
(In reply to Ian Delaney from comment #1) dev-python/paramiko has an unstated optional runtime dependency on net-misc/openssh. The solution to this bug is to stabilize a newer version of paramiko. There are several bugs open to stabilize newer paramiko; apparently nobody searches for bugs these days.
Current stable is 1.15.1. Does this issue still exist there?
