View previous topic :: View next topic |
Author |
Message |
glirk n00b
Joined: 27 May 2004 Posts: 12
|
Posted: Sat Jun 05, 2004 11:17 pm Post subject: SSH Secure Shell 3.2.9.1 |
|
|
Anyone have a clue why a user would be told by ssh that their password is incorrect, only to try again 30 min later and have it work?
I have not changed a thing. Since they get the password prompt either way, I assume it's not an intermittent network problem.
Simply waiting may turn your failure into a success when logging into my box.
I use ssh provided by ssh.com (not openssh, yes I know I *can* use openssh - but am concerned wrt security).
Code: | [root@tron:/home/cr]$ ssh -V
ssh: SSH Secure Shell 3.2.9.1 (non-commercial version) on i686-pc-linux-gnu |
I also can't seem to connect to any ssh servers other than my own. I have tried to connect to a friend's machine running the same version of ssh as I am, and I have also tried a Solaris 10 box with Sun's ssh. The ssh client hangs until I ctrl-c, and gives me this:
Code: | Received signal 2. (no core) |
I've been thru my config files and the relevant FAQ's/manuals, but cannot find a way to fix either of these problems.
TIA.
ps: If your answer contains the words "use" and "openssh" just save your time. I know openssh works, I've tested it. I'm curious about this version of ssh. |
|
Back to top |
|
|
hifidelity n00b
Joined: 17 Oct 2002 Posts: 17
|
Posted: Tue Jun 08, 2004 5:51 am Post subject: |
|
|
well starting out i would say... Support free software and use openssh!
as for your problem, its possible that maybe updating to a more recent version of pam may work? i don't know if that version of ssh uses pam, but its worth a try maybe using one of the newer ~unstable pam packages. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|