l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2006 Jul 20 19:38

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] SSH Troubles
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] SSH Troubles

Marc Elliot Hall wrote:
> Today I've been trying to connect to my SSH server, and although I can
> connect using SSH via my LAN, when I attempt to connect from my work 
> machine, or even while I'm at home through my VLAN, the connection 
> fails.
> Generally I use PuTTY (Release 0.58) for this with no problems. Today, 
> though, the connection fails and PuTTY says:
> "Server's host key did not match the signature supplied"
> A Google search reveals this page:
> http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/host-key-sig-verify-fail.html
> which describes it as a difficult-to-reproduce bug, although it is still
> unclear whether the bug is in PuTTY or in the SSH server.
> So I thought, "okay, if it's possibly a PuTTY problem. I'll try a
> different SSH client." After installing SecureCRT (Version 4.1.9 (build
> 278)) and attempting to connect, SecureCRT says:
> "The server's host key failed to verify."
> Googling on that phrase generates a single PDF link, which simply
> recommends that one should use PuTTY, completely failing to adequately
> address the issue.
> Not one to give up easily, I then used the Cygwin SSH client to attempt
> a connection. (Cygwin OpenSSH_4.3p2, OpenSSL 0.9.8a 11 Oct 2005)
> Cygwin says:
> $ ssh -p21 me@mydomain.com
> RSA_public_decrypt failed: error:0407006A:rsa
> routines:RSA_padding_check_PKCS1_type_1:block type is not 01
> key_verify failed for server_host_key
> I have restarted the ssh daemon as well as my Netgear firewall/router 
> appliance, and get the same results. 
> Since I routinely apt-get update my Debian Testing server, including
> yesterday, I suspect this issue may be related to a recent change in
> sshd. I also rebooted the machine yesterday due to an updated kernel. 
> Linux 2.6.15-1-686
> OpenSSH_4.3p2 Debian-2, OpenSSL 0.9.8b
> Any ideas?
While not much help, I've noticed sometimes when do apt-get updates
especially major releases my config files get scrambled and things stop
working. Take a look with a text editor at some of your ssh config files
in /etc/ssh and see if anything looks like gibberish.
I've had this problem with apache, zope and a few other things mostly
when I did an OS upgrade between versions.

You could also try to roll back to the previous version and see if it
works then.


My apologies, I'm just a fool stumbling in the dark.

vox-tech mailing list

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
Sunset Systems
Who graciously hosts our website & mailing lists!