I can reproduce this using the version in salsa also:
bash5$ ssh -F/dev/null -oUserKnownHostsFile=/dev/null
-oStrictHostKeyChecking=no root@localhost -p2022 dpkg-query -W base-files
tinysshd linux-image-cloud-amd64
Warning: Permanently added '[localhost]:2022' (ED25519) to the list of
known hosts.
base-files 11.1
linux-image-cloud-amd64 5.10.46-5
tinysshd 20210601-1
bash5$ screen ssh -F/dev/null -oUserKnownHostsFile=/dev/null
-oStrictHostKeyChecking=no root@localhost -p2022 -oControlMaster=auto
-oControlPath=~/.ssh/master-%C -oControlPersist=3600
bash5$ screen ssh -F/dev/null -oUserKnownHostsFile=/dev/null
-oStrictHostKeyChecking=no root@localhost -p2022 -oControlMaster=auto
-oControlPath=~/.ssh/master-%C -oControlPersist=3600
bash5$ ssh -F/dev/null -oUserKnownHostsFile=/dev/null
-oStrictHostKeyChecking=no root@localhost -p2022 systemctl --state=failed
Warning: Permanently added '[localhost]:2022' (ED25519) to the list of
known hosts.
UNIT LOAD ACTIVE SUB
DESCRIPTION
● tinysshd@1-10.0.2.15:22-10.0.2.2:38228.service loaded failed failed Tiny
SSH server (10.0.2.2:38228)
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
1 loaded units listed.
bash5$ ssh -F/dev/null -oUserKnownHostsFile=/dev/null
-oStrictHostKeyChecking=no root@localhost -p2022 systemctl status
tinysshd@1-10.0.2.15:22-10.0.2.2:38228.service
Warning: Permanently added '[localhost]:2022' (ED25519) to the list of
known hosts.
● tinysshd@1-10.0.2.15:22-10.0.2.2:38228.service - Tiny SSH server
(10.0.2.2:38228)
Loaded: loaded (/lib/systemd/system/tinysshd@.service; disabled;
vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2021-09-27 14:56:27 AEST;
18s ago
TriggeredBy: ● tinysshd.socket
Docs: man:tinysshd
Process: 414 ExecStartPre=/usr/sbin/tinysshd-makekey -q
/etc/tinyssh/sshkeydir (code=exited, status=111)
Process: 415 ExecStart=/usr/sbin/tinysshd ${TINYSSHDOPTS} --
/etc/tinyssh/sshkeydir (code=exited, status=111)
Main PID: 415 (code=exited, status=111)
CPU: 193ms
Sep 27 14:56:26 main.lan systemd[1]: Starting Tiny SSH server
(10.0.2.2:38228)...
Sep 27 14:56:26 main.lan systemd[1]: Started Tiny SSH server
(10.0.2.2:38228).
Sep 27 14:56:26 main.lan tinysshd[415]: tinysshd: 9ZEQRTtP: info:
connection from 10.0.2.2:38228 {main_tinysshd.c:106}
Sep 27 14:56:26 main.lan tinysshd[415]: tinysshd: 9ZEQRTtP: info: auth:
root: ssh-ed25519
AAAAC3NzaC1lZDI1NTE5AAAAIIapAZ0E0353DaY6xBnasvu/DOvdWdKQ6RQURwq4l6Wu accepted
{packet_auth.c:155}
Sep 27 14:56:27 main.lan tinysshd[415]: tinysshd: 9ZEQRTtP: BUG: (protocol
error){channel.c:57}
Sep 27 14:56:27 main.lan systemd[1]:
tinysshd@1-10.0.2.15:22-10.0.2.2:38228.service: Main process exited,
code=exited, status=111/n/a
Sep 27 14:56:27 main.lan systemd[1]:
tinysshd@1-10.0.2.15:22-10.0.2.2:38228.service: Failed with result 'exit-code'.
Sep 27 14:56:27 main.lan systemd[1]:
tinysshd@1-10.0.2.15:22-10.0.2.2:38228.service: Unit process 418 (bash) remains
running after unit stopped.
