Re: SSH 5.3 Problems

2005-01-06 Thread Duane Winner
Brian McCann wrote:
Hi all.  On 5.3 and 5.3 RC1 I have this problem where when I ssh in
using either a FreeBSD 4.3 box or an older PuTTY client (0.52 is one I
experienced it with), I cannot connect.  On PuTTY, it asks for a
username, then just exits. On FreeBSD when I put the ssh client into
verbose, it appears it can't agree on an auth method, even though both
are set to accept and attempt keyboard-interactive.  Upgrading to a
newer PuTTY fixed the problem, and it seams to work from FreeBSD 4.10.
I've seen some posts from people that upgrading their PuTTY fixed the
problem, but I'm curious if anyone knows the cause of the problem, and
possibly how to fix it, on the server end.
Thanks,
--Brian McCann
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
 

For what it's worth, we happen to have some licensed copies of the 
commercial SSH client (from SSH Communications Inc.) for our Windows 
boxes. I just tried to reproduce this problem. To ssh into *nix 
workstations, I've always just used password authentication.

On the commercial windows client, after you specify the hostname and 
username, you pick from a drop-down list Authentication Method:
-Password
-Public Key
-SecureID
-PAM
-Keyboard Interactive

I have ALWAYS just used password to get into my Linux and FreeBSD 
workstations running sshd. But password no longer works. I started to 
get nervous, but relaxed when I found out that if I selected Keyboard 
Interactive, I could get in.

I don't understand what exacactly keyboard interactive is and how it 
differs from password, but it seems to work.

I haven't used PuTTY in a few years, and I don't know if this is 
something that can be tweaked or not.

Cheers,
DW
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: SSH 5.3 Problems

2005-01-06 Thread Lowell Gilbert
Duane Winner [EMAIL PROTECTED] writes:

 I don't understand what exacactly keyboard interactive is and how it
 differs from password, but it seems to work.

The latter doesn't go through PAM.

 I haven't used PuTTY in a few years, and I don't know if this is
 something that can be tweaked or not.

Recent versions certainly can do keyboard-interactive.

-- 
Lowell Gilbert, embedded/networking software engineer, Boston area
http://be-well.ilk.org/~lowell/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: SSH 5.3 Problems

2005-01-04 Thread David Landgren
Brian McCann wrote:
Hi all.  On 5.3 and 5.3 RC1 I have this problem where when I ssh in
using either a FreeBSD 4.3 box or an older PuTTY client (0.52 is one I
experienced it with), I cannot connect.  On PuTTY, it asks for a
username, then just exits. On FreeBSD when I put the ssh client into
verbose, it appears it can't agree on an auth method, even though both
are set to accept and attempt keyboard-interactive.  Upgrading to a
newer PuTTY fixed the problem, and it seams to work from FreeBSD 4.10.
 I've seen some posts from people that upgrading their PuTTY fixed the
problem, but I'm curious if anyone knows the cause of the problem, and
possibly how to fix it, on the server end.
What error message does sshd emit on the server?
David
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: SSH 5.3 Problems

2005-01-04 Thread Rob
Brian McCann wrote:
Hi all.  On 5.3 and 5.3 RC1 I have this problem where when I ssh in
using either a FreeBSD 4.3 box or an older PuTTY client (0.52 is one I
experienced it with), I cannot connect.  On PuTTY, it asks for a
username, then just exits. On FreeBSD when I put the ssh client into
verbose, it appears it can't agree on an auth method, even though both
are set to accept and attempt keyboard-interactive.  Upgrading to a
newer PuTTY fixed the problem, and it seams to work from FreeBSD 4.10.
 I've seen some posts from people that upgrading their PuTTY fixed the
problem, but I'm curious if anyone knows the cause of the problem, and
possibly how to fix it, on the server end.

Same problem occurred here with other SSH programs for Windows that
connect to FreeBSD PC. When upgrading from 4.10 to 5.3, suddenly the
Windows PCs could not connect anymore , with a similar error as you
get. Upgrading was the solution. I never tried to downgrade the newer
SSH version on FreeBSD to handle old versions; I considered the reverse
a better way :).
Curiously: a nother PC running 4.10 had no problems to connect to 5.3.
Only Windows' SSH programs had such problems.
Rob.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: SSH 5.3 Problems

2005-01-04 Thread Brian McCann
That's just it...I didn't see any errors.  Originally it was throwing
errors that it couldn't lookup the name of the workstation, but once
that got fixed I wasn't getting anything.  I've got to try putting
sshd into verbose later this afternoon...

--Brian


On Tue, 04 Jan 2005 15:14:33 +0100, David Landgren [EMAIL PROTECTED] wrote:
 Brian McCann wrote:
  Hi all.  On 5.3 and 5.3 RC1 I have this problem where when I ssh in
  using either a FreeBSD 4.3 box or an older PuTTY client (0.52 is one I
  experienced it with), I cannot connect.  On PuTTY, it asks for a
  username, then just exits. On FreeBSD when I put the ssh client into
  verbose, it appears it can't agree on an auth method, even though both
  are set to accept and attempt keyboard-interactive.  Upgrading to a
  newer PuTTY fixed the problem, and it seams to work from FreeBSD 4.10.
   I've seen some posts from people that upgrading their PuTTY fixed the
  problem, but I'm curious if anyone knows the cause of the problem, and
  possibly how to fix it, on the server end.

 What error message does sshd emit on the server?

 David

 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: SSH 5.3 Problems

2005-01-04 Thread Brian McCann
Tried that I set PuTTY to use only V2 and it died as well.  I
guess it's possible that older versions of PuTTY has an SSH v2 bug,
but it happened from FreeBSD trying that too. :-/

Thanks though,
--Brian


On Tue, 4 Jan 2005 10:17:34 -0800, Aaron Nichols [EMAIL PROTECTED] wrote:
 On Tue, 4 Jan 2005 10:16:37 -0500, Brian McCann [EMAIL PROTECTED] wrote:
  That's just it...I didn't see any errors.  Originally it was throwing
  errors that it couldn't lookup the name of the workstation, but once
  that got fixed I wasn't getting anything.  I've got to try putting
  sshd into verbose later this afternoon...
 
 Note that as of 5.x only protocol version 2 is supported by default.
 Thus, you may want to try changing the following line in
 /etc/ssh/sshd_config:
 
 from:
 #Protocol 2
 
 to:
 Protocol 2,1
 
 This will enable ssh1 support
 
 Aaron

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]