[SOLVED] Re: Enabling SSD
- In reply to: Paul M Foster : "Enabling SSD"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 30 Jan 2024 04:55:55 UTC
On Mon, Jan 29, 2024 at 11:32:05PM -0500, Paul M Foster wrote: > Folks: > > Fresh install of FreeBSD 14. The following changes in /etc/ssh/sshd_config: > > LogLevel DEBUG > PermitRootLogin yes > PubkeyAuthentication no > PasswordAuthentication yes > KbdInteractiveAuthentication no > > No modifications have been made to other files, including the PAM files. > > My intent is to insist on password, not public key authentication. Root > login is more or less irrelevent, just convenient. > > Regardless of edits to the file, or which user, attempts to login from > elsewhere on the LAN fail. The response on the client side: I'm not asked > for a password at all. The connection just closes. This client has > consistently been able to SSH into other Linux clients on this LAN. It's > based on the latest Debian, so it's particularly out of date. > > Here are the relevant lines from auth.log: > > Jan 30 03:24:22 buckaroo sshd[3121]: Connection from 192.168.254.20 port > 60568 on 192.168.254.30 port 22 > Jan 30 03:34:22 buckaroo sshd[3121]: Connection closed by authenticating > user paulf 192.168.254.20 port 60568 [preauth] > > The last line puzzles me. Does this mean that the *client* closed the > connection? If so, any guesses why? If this is no help, any other reasons > why SSH is not working properly? > > Paul > Well, I solved it. On the CLIENT, in the ~/.ssh/config, I had: PasswordAuthentication no When I changed this value to yes, it all worked. Thanks to all who attempted to help. It is appreciated. Paul -- Paul M. Foster Personal Blog: http://noferblatz.com Company Site: http://quillandmouse.com Software Projects: https://gitlab.com/paulmfoster