On Wed, 2009-06-17 at 10:55 +0200, Arthur Lutz wrote:
> Package: clusterssh
> Version: 3.26-1
> Severity: normal
>
>
> After upgrading from 3.25 to 3.26
>
> 2009-06-16 15:59:33: upgrade clusterssh=3.25-1 3.26-1
>
> I get an authenticity check on almost all the hosts I connect to using cssh :
>
> The authenticity of host XXX can't be established.
> RSA key fingerprint is YYYY
> Are you sure you want to continue connecting (yes/no)
>
> Yet, using normal ssh the hosts are correctly referenced in known_hosts.
>
> Does cssh use a different known_hosts ? If so, why ? If not, why do I get
> these
> (kind of scary) warnings ?
I have not run across this behavior, although I do connect to hosts
using SSH hostnames (that is, names that are only found in .ssh/config).
Is is possible that names are now being looked up in .ssh/config that
were previously resolved by /etc/hosts or DNS? I believe the order of
host resolution may have changed based on this entry in the Changelog:
* Fix bug with some host lookups failing
The corresponding change in the source is:
Index: cssh.pl
===================================================================
--- cssh.pl (revision 262)
+++ cssh.pl (revision 263)
@@ -955,11 +958,11 @@
else {
logmsg( 1,
"Failed to check host (falling back to gethostbyname):
$!" );
- return gethostbyname($host);
+ return gethostbyname($host)->name();
}
}
else {
- return gethostbyname($host);
+ return gethostbyname($host)->name();
}
}
If you are still having problems with this, perhaps you could send debug
output (--debug 2 for v3.26, -dD for v3.25) of the connection attempt.
If it involves any specific host information, you can send it directly
to my maintainer address instead of to the bug report.
Thank you,
Tony Mancill
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
