You are not logged in.
SSH - Connection to x.x.x.x closed by remote host. - privsep_preauth: preauth child terminated by signal 31
Since some weeks I'm having following problem. Starting with
I started /usr/bin/sshd -Dddd
my logs look fine, until authentification is done.
Both seem to work, password and key, but then suddenly the error:
...
debug3: PAM: do_pam_account pam_acct_mgmt = 0 (Success)
debug3: mm_request_send entering: type 103
Accepted password for eder from 10.0.0.76 port 40898 ssh2
debug1: monitor_child_preauth: eder has been authenticated by privileged process
debug3: mm_get_keystate: Waiting for new keys
debug3: mm_request_receive_expect entering: type 26
debug3: mm_request_receive entering
debug3: mm_get_keystate: GOT new keys
debug3: mm_auth_password: user authenticated [preauth]
debug3: mm_do_pam_account entering [preauth]
debug3: mm_request_send entering: type 102 [preauth]
debug3: mm_request_receive_expect entering: type 103 [preauth]
debug3: mm_request_receive entering [preauth]
debug3: mm_do_pam_account returning 1 [preauth]
debug3: send packet: type 52 [preauth]
debug3: mm_request_send entering: type 26 [preauth]
debug3: mm_send_keystate: Finished sending state [preauth]
debug1: monitor_read_log: child log fd closed
privsep_preauth: preauth child terminated by signal 31
debug1: do_cleanup
debug3: PAM: sshpam_thread_cleanup entering
My /etc/ssh/sshd.conf is 100% original, as it comes from the installation package.
I have no firewall installed and there are no hosts_allowed or hosts_denied.
Did anyone else stumble about this problem?
Offline
I doubt anyone will be able to help you here at present as there are a few problems with your post.
You haven't said if you are using Arch as a ssh server or as a client or both.
You haven't posted any version details of installed packages and you have only posted a small section of debug output.
My /etc/ssh/sshd.conf is 100% original, as it comes from the installation package.
There is no /etc/ssh/sshd.conf file in Arch.
...and there are no hosts_allowed or hosts_denied.
Unless you have been tinkering...
https://www.archlinux.org/news/dropping … s-support/
Perhaps take a read of...
https://wiki.archlinux.org/index.php/Co … orrectness
Kind regards
Paul.
Offline
Yes, you are right! My mistake! So here my specifications:
my Arch Linux is up to date, I nearly daily run an update
Kernel: 4.10.13-1
openssh: 7.5p1-2
Running as a client, it works perfect, I can access other devices.
The problem comes with accessing this system through the server.
I activated the service in systemd as sshd.socket, but the problem occurs as sshd.service too, the same, if I just start it manual.
Yes, there is no such file, I mentioned above, the right name is: /etc/ssh/sshd_config
It is still 100% original, I purged openssh completely and reinstalled it. Optional I installed mosh and sshfs, but the problem persists, if I uninstall these 2 packages.
The problem occured first time, when the last Gnome3 update came. I remember it, because I normally try to postpone that for a few weeks, so I blocked the gnome group in pacman. But then I got update problems with some cryptographic libraries, which I sadly don't remember anymore. So I decided to run the full update, including Gnome Shell (3.24.2-1). Since then openssh client is running again, but the server ain't accessible anymore.
After interpreting the logs, it seems to me like a successful authentication but then SSH fails to establish the connection and operation. But no further warning.
Offline
The problem occured first time, when the last Gnome3 update came. I remember it, because I normally try to postpone that for a few weeks, so I blocked the gnome group in pacman. But then I got update problems with some cryptographic libraries, which I sadly don't remember anymore. So I decided to run the full update, including Gnome Shell (3.24.2-1). Since then openssh client is running again, but the server ain't accessible anymore.
Could it be a partial upgrade problem? ssh will obviously use cryptographic libraries, so perhaps check you haven't messed those packages up by verifying your installed packages.
I've always stuck to running ssh as a service rather than a socket and it's always worked perfectly for me. When running as a service, is there anything in the journal?
Offline