On Thu, May 17, 2001 at 09:47:15PM -0700, Leo Clark wrote: > During the last day or two sshd has stoped working on my server. It lets > you connect and it denies bad account/password combinations. If you login > right then it just disconnects you right away. > > So I tried killing and restarting the service. I got this error message > when I launched it and it starting running with the same simptoms as > before. > > error: ConnectionsPerPeriod has been deprecated! Did the config files get updated? Usually an error that says something is deprecated means you're trying to pass obsolete options to the program. > > So I tried restarting the box (I know, I know, it's not windows but I'm > grabing at straws.). So i tried everything I did before and I noticed > something being dumped to the console when I tried to connect: > > May 17 21:30:43 drivesac sshd[309]: no modules loaded for `sshd' service > May 17 21:30:43 drivesac sshd[309]: fatal: PAM session setup failed[6]: Permission >denied > May 17 21:30:43 drivesac sshd[309]: no modules loaded for `sshd' service > > I just cvsup'd to 4.3 2 days ago. I'm pretty sure it was worked since > then but I'm not 100%. Anyone have any ideas? Thanks. > RELENG_4_3? Should be OpenSSH 2.3.0, what was it before? Make sure both machines agree on which protocol to use. It also looks like your pam config files are out of whack. I have never used FreeBSD, but on an OpenBSD system, I would do something like: diff -u /etc/sshd_config /usr/src/usr.bin/ssh/sshd_config and diff -u /etc/ssh_config /usr/src/usr.bin/ssh/ssh_config and look at the changes. Do the same type of thing for the pam configs. (OpenBSD doesn't have pam; I don't off-hand remember the setup for Linux :) If that doesn't turn up anything, move the ~/.ssh directory to ~/.ssh.old for the user(s) you are testing connectivity with on both machines. See if something there is causing problems. <[EMAIL PROTECTED]>
