Bug#334982: known_hosts should record nonstandard ports
Package: ssh
Version: 1:3.8.1p1-8.sarge.4
Severity: wishlist
File: /usr/bin/ssh
There are situations where different ports on a host will lead to
different sshds with different host keys - for example, if the host
forwards lots of ports to other machines' sshd servers.
When connecting to several of these, ssh forces one to either use
separate UserKnownHostFiles for each, or editing .ssh/known_hosts every
time.
If the port used is not the standard port, noting that port in the
known_hosts file and only matching entries with that port would solve
this issue.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8+lisbeth.20050206
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages ssh depends on:
ii adduser 3.63 Add and remove users and groups
ii debconf 1.4.30.13 Debian configuration management sy
ii dpkg 1.10.28 Package maintenance system for Deb
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii libpam-modules 0.76-22 Pluggable Authentication Modules f
ii libpam-runtime 0.76-22 Runtime support for the PAM librar
ii libpam0g 0.76-22 Pluggable Authentication Modules l
ii libssl0.9.7 0.9.7e-3 SSL shared libraries
ii libwrap0 7.6.dbs-8 Wietse Venema's TCP wrappers libra
ii zlib1g 1:1.2.2-4.sarge.2 compression library - runtime
-- debconf information:
ssh/insecure_rshd:
* ssh/privsep_ask: true
* ssh/user_environment_tell:
* ssh/forward_warning:
* ssh/insecure_telnetd:
* ssh/new_config: true
* ssh/use_old_init_script: true
ssh/rootlogin_warning:
* ssh/upgrade_to_openssh: true
* ssh/SUID_client: true
ssh/disable_cr_auth: false
* ssh/privsep_tell:
* ssh/ssh2_keys_merged:
ssh/ancient_version:
* ssh/protocol2_only: true
ssh/encrypted_host_key_but_no_keygen:
* ssh/run_sshd: true
Reply to: