#773882 ssh_exchange_identification: read: Connection reset by peer

Package:
xinetd
Source:
xinetd
Description:
replacement for inetd with many enhancements
Submitter:
ael
Date:
2014-12-24 17:00:07 UTC
Severity:
normal
#773882#5
Date:
2014-12-24 16:56:23 UTC
From:
To:
Dear Maintainer,

I have been running sshd from xinetd with

service ssh
{
	disable		=  no
	socket_type	=  stream
	wait		=  no
	user		=  root
	server		=  /usr/sbin/sshd
	protocol	=  tcp
	log_on_failure	+= USERID
	only_from	=  192.168.0.0/29 192.168.10.0/29
}

without problems for some years. This has recently stopped working: if a
("only_from") client tries to connect, something like this happens:
--------------------
$ ssh -vX ael@conquest2
OpenSSH_6.7p1 Debian-3, OpenSSL 1.0.1j 15 Oct 2014
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to conquest2 [192.168.0.2] port 22.
debug1: Connection established.
debug1: key_load_public: No such file or directory
debug1: identity file /home/ael/.ssh/id_rsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/ael/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/ael/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/ael/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/ael/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/ael/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/ael/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/ael/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.7p1 Debian-3
ssh_exchange_identification: read: Connection reset by peer
--------------------

Removing sshd from xinetd and running it standalone on this same machine
with no other changes solves the problem.