Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 29 Jan 2024 23:32:05 -0500
From:      Paul M Foster <paulf@quillandmouse.com>
To:        freebsd-questions@freebsd.org
Subject:   Enabling SSD
Message-ID:  <20240130043205.2japt7ja7j5urm5r@yosemite.mars.lan>

next in thread | raw e-mail | index | archive | help
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

-- 
Paul M. Foster
Personal Blog: http://noferblatz.com
Company Site: http://quillandmouse.com
Software Projects: https://gitlab.com/paulmfoster



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20240130043205.2japt7ja7j5urm5r>