Hi, This is for 3.1p2, but it is not in Bugzilla version system yet! The last many years I have been tunneling ssh through ssh. What I do is to ssh to a special port on my localhost. This port is then (using ssh :-) ) forwarded to a remote ssh server. This has worked perfect for a long time! Until my upgrade to 3.1p2 the ssh1 system correctly asked the remote server at the end of the line for a name (and a host key). The remote server name was the key in the host table. Now, however, ssh saves the key under localhost!!! This is really uncool since I easily run five tunnels to five different remote servers (on five local port no's), so...... Whoever changed it.... Is this a bug, or am I using ssh in the wrong way! Thanks, - Jakob Lichtenberg
the pre-3.x behaviour can be restored with this option: NoHostAuthenticationForLocalhost This option can be used if the home directory is shared across machines. In this case localhost will refer to a different ma- chine on each of the machines and the user will get many warnings about changed host keys. However, this option disables host au- thentication for localhost. The argument to this keyword must be ``yes'' or ``no''. The default is to check the host key for lo- calhost. however, the use of HostKeyAlias is recommended
Mass change of RESOLVED bugs to CLOSED