On Thu, 27 Apr 2023, Tomas Kuchta wrote:
You can stop the sshd service on the server, then start it interactively with -vvvv - then try connecting from the client to see the server response in your server shell.
Tomas, et al.: I found the problem and it will take me a while to fix it. It's related to user authentication. On 18 May 2020 Pat added PAM to Slackware64-current and it's now part of 15.0; alienbob reported this on his blog. There's PAM and PAM-kbr5 (for Kerberos). PAM requires three packages, PAM, Cracklib, and libpwquality. While PAM and Cracklist are in the PACKAGES.TXT list in the Slackware64-15.0 source tree, I don't find either installed on the laptop. The other side of this issue is that PAM is not available for Slackware64-14.2; it's brand new with -15.0. I don't know if this makes a difference because while salmo's syslogs and secure logs have no entries relating to ssh or sshd, caddis' do. There are a few entries in syslog* but many in the secure logs. Example: Apr 22 17:24:31 caddis sshd[1388]: gkr-pam: unable to locate daemon control file Apr 22 17:24:31 caddis sshd[1388]: gkr-pam: stashed password to try later in open session Apr 22 17:24:31 caddis sshd[1385]: pam_unix(sshd:session): session opened for user rshepard(uid=1000) by (uid=0) Apr 22 17:24:31 caddis sshd[1385]: gkr-pam: unable to locate daemon control file Apr 22 17:24:31 caddis sshd[1385]: gkr-pam: gnome-keyring-daemon started properly So, at least for the next couple of days I'll continu using a 32G USB flash drive to exchange files between the two host because I've client work that has a higher priority. Thanks, everyone. Regards, Rich
