Bug#682050: Semantics of known_hosts

2012-11-06 Thread Lars Noschinski
As far as I can gather from readin sshd(8) and the source code (get_hostfile_hostname_ipaddr in upstream's openssh-6.1p1), at most two key lookups are performed: (a) [Only for protocol version 1] One for the ip address of the remote host, with put_host_port(ntop, port) (b) One for the

Bug#682050: fails to connect to server using non default port

2012-11-03 Thread Lars Noschinski
I agree with Josh's assessment. As I noted in 668239, different host keys for different ports on the same server are clearly documented in the OpenSSH man page. Hence, the assessment in the initial bugreport and hostkey.patch are clearly wrong. I tested dropping hostkey.patch and this makes

Bug#668239: host key handling broken when port!=22

2012-07-30 Thread Lars Noschinski
Package: python-paramiko Version: 1.7.7.1-3 Followup-For: Bug #668239 Dear Maintainer, this patch does not fix the issues with duplicity; in fact, I believe this change is wrong. As of openssh-server-1:6.0p1-2 0, sshd(8) states for the ~/.ssh/known_hosts file: A hostname or address may