Chris Green wrote:
So, why doesn't the first one work? I think I've set everything up but I may have missed something obvious. Any ideas anyone?
Chris, sorry if you wrote you did this and I didn't spot it (digests are cumbersome to follow), but have you changed the "Password Authentication" line in /etc/ssh/sshd_config file? Jen
______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
On Tue, Feb 24, 2004 at 09:27:11AM -0000, Jenny Hopkins wrote:
Chris Green wrote:
So, why doesn't the first one work? I think I've set everything up but I may have missed something obvious. Any ideas anyone?
Chris, sorry if you wrote you did this and I didn't spot it (digests are cumbersome to follow), but have you changed the "Password Authentication" line in /etc/ssh/sshd_config file? Jen
It's actually /etc/ssh2/sshd2_config, the relevant bits of the file are:-
# DEPRECATED PubkeyAuthentication yes # AllowedAuthentications publickey,password,hostbased AllowedAuthentications publickey,password # #RequiredAuthentications publickey,password
So it looks like public key authentication is allowed.
I'm wondering if it's an incompatibility between the client ssh (most of the ones I'm trying are OpenSSH version 3.4.x) and the server ssh which reports itself as SSH Version 2.0.13.
On Tue, Feb 24, 2004 at 11:25:35AM +0000, Chris Green chris@areti.co.uk wrote:
I'm wondering if it's an incompatibility between the client ssh (most of the ones I'm trying are OpenSSH version 3.4.x) and the server ssh which reports itself as SSH Version 2.0.13.
Ow, that's old ! Have you tried to start the sshd server in debugging mode ? You can easily do something like sshd -p 2222 -d -d -d -D. It usually helps a lot to save problems.
Lucas
On Tue, Feb 24, 2004 at 04:10:54PM +0100, Lucas Nussbaum wrote:
On Tue, Feb 24, 2004 at 11:25:35AM +0000, Chris Green chris@areti.co.uk wrote:
I'm wondering if it's an incompatibility between the client ssh (most of the ones I'm trying are OpenSSH version 3.4.x) and the server ssh which reports itself as SSH Version 2.0.13.
Ow, that's old ! Have you tried to start the sshd server in debugging mode ? You can easily do something like sshd -p 2222 -d -d -d -D. It usually helps a lot to save problems.
I'm not sure that it's that old, it's just not openSsh, it's the commercial one I think. The man page has:-
AUTHORS SSH Communications Security Ltd.
at the bottom.
When I try sshd -p 2222 -d -d -d -D (well, with just some of those Dd) I get:-
WARNING: sshd: Failed to read config file /home/cgreen/.ssh2/sshd2_config WARNING: Development-time debugging not compiled in. WARNING: To enable, configure with --enable-debug and recompile. debug: Reading private host key from /home/cgreen/.ssh2/hostkey sshd[9014]: FATAL ERROR: ssh_privkey_read from /home/cgreen/.ssh2/hostkey failed. FATAL: ssh_privkey_read from /home/cgreen/.ssh2/hostkey failed.
(It's installed in /etc/alternatives for some reason!).
It *might* be worth getting my own personal copy of openSsh as I believe it can run (for a single user) without root privilege.
-
Chris Green -
Jenny Hopkins -
Lucas Nussbaum