I run 5 boxes with ssh here. If you want, I will post the configuration file onto the mailing list, so you can try it. The file is updated to avoid the notorious openssh exploit, even if you have not patched up your ssh (however, it seems you have the latest version, which I think doesn't have the problem.)
Stuff like this always means some small obscure detail. I once spent a whole day hacking, it turned out a config file had a period instead of a comma :) Alex PS: if you (D. Brown) reply in 5 minutes, I will also post my /etc/shadow file </corny joke> PPS: Thanks for the advice about the distros. I downloaded gcc 3.1, so the problem is gone, BUT now I have two versions, and I must remember which one to use. Hoping RH comes out with a solid 7.4/8.0 with no gimmicks. Daniel Brown wrote: > i upgraded openssl and consequently had to recompile openssh, so i > figured i would just compile+install the newest version of it (openssh). > ive done this on 2 of my 3 machines, and now i cannot ssh into them > (have to run telnet for the time being) > > when i attempt to `ssh host` (into a new (3.4p1) sshd), it: > > might complain if ~/.ssh/known_hosts lists a key different than the one > that host is providing (due to recurring reinstallation), and this is > remedied by taking that hosts entry out of the known_hosts file > > prompts for authentication, lets me try 3 times (the default), but wont > authenticate my password. this occurs when trying to login to both > updated hosts with multiple user accounts. my remaining un-updated box > will still allow logins > > ive looked (and am still looking) thru the sshd_config file, and cant > find the DenyUserRegardlessOfPassword option. any insights? > > thanks > _______________________________________________ Siglinux mailing list [EMAIL PROTECTED] http://www.utacm.org/mailman/listinfo/siglinux
