通过xinetd托管SSH服务时遭遇kex_exchange_identification连接重置错误的求助

我有两台运行Ubuntu 22.04.2 LTS的服务器，都安装了openssh-server 1:8.9p1-3ubuntu0.1，并且两台服务器上都创建了相同的管理员用户。

我想测试传统超级守护进程xinetd来托管SSH服务，于是在第一台服务器上停止了ssh.service，添加了以下配置文件后启动了xinetd.service：

cat /etc/xinetd.d/ssh

service ssh
{
disable     = no
socket_type = stream
protocol    = tcp
wait        = no
user        = root
server      =/usr/sbin/sshd
server_args = -1
flags       = IPv4
interface   = 192.168.50.100
}

按照预期，当我尝试SSH连接这台运行xinetd的服务器时，xinetd应该启动SSH守护进程并允许我登录，但我却遇到了如下错误：

ssh -v 192.168.50.100

OpenSSH_8.9p1 Ubuntu-3ubuntu0.1, OpenSSL 3.0.2 15 Mar 2022
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug1: Connecting to 192.168.50.100 [192.168.50.100] port 22.
debug1: Connection established.
debug1: identity file /home/thomasgrusz/.ssh/id_rsa type -1
debug1: identity file /home/thomasgrusz/.ssh/id_rsa-cert type -1
debug1: identity file /home/thomasgrusz/.ssh/id_ecdsa type -1
debug1: identity file /home/thomasgrusz/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/thomasgrusz/.ssh/id_ecdsa_sk type -1
debug1: identity file /home/thomasgrusz/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file /home/thomasgrusz/.ssh/id_ed25519 type -1
debug1: identity file /home/thomasgrusz/.ssh/id_ed25519-cert type -1
debug1: identity file /home/thomasgrusz/.ssh/id_ed25519_sk type -1
debug1: identity file /home/thomasgrusz/.ssh/id_ed25519_sk-cert type -1
debug1: identity file /home/thomasgrusz/.ssh/id_xmss type -1
debug1: identity file /home/thomasgrusz/.ssh/id_xmss-cert type -1
debug1: identity file /home/thomasgrusz/.ssh/id_dsa type -1
debug1: identity file /home/thomasgrusz/.ssh/id_dsa-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.1
debug1: kex_exchange_identification: banner line 0: unknown option -- 1
kex_exchange_identification: read: Connection reset by peer
Connection reset by 192.168.50.100 port 22

有没有大佬知道问题出在哪？

备注：内容来源于stack exchange，提问作者Thomas Grusz