What were you trying to do that didn't work?

Using EPEL tcpd with sshd

What is the impact of this issue to you?

Cannot be paranoid

Please provide the package NVR for which the bug is seen:

How reproducible is this bug?:

Always

Steps to reproduce

1. Install EPEL tcpd
2. sudo setsebool -P ssh_use_tcpd=1
3. sudo systemctl stop sshd
4. sudo systemctl disable sshd
5. sudo cp etc/hosts.deny /etc/hosts.deny
6. edit /etc/systemd/system/sshd@.service with:
   ExecStart=@-/usr/sbin/tcpd /usr/sbin/sshd -D $OPTIONS
7. sudo systemctl enable --now sshd.socket
8. ssh localhost

Expected results

sshd should just bind with socket

Actual results

Dec 9 14:34:36 dns3 systemd[1]: Failed to start OpenSSH per-connection server daemon.
Dec 9 14:34:36 dns3 systemd[1]: Stopped OpenSSH per-connection server daemon.
Dec 9 14:34:36 dns3 systemd[1]: sshd@133-127.0.0.1:22-127.0.0.1:49008.service: Got no socket.
Dec 9 14:34:36 dns3 systemd[1]: sshd@133-127.0.0.1:22-127.0.0.1:49008.service: Failed to run 'start' task: Invalid argument
Dec 9 14:34:36 dns3 systemd[1]: sshd@133-127.0.0.1:22-127.0.0.1:49008.service: Failed with result 'resources'.
Dec 9 14:34:36 dns3 systemd[1]: Failed to start OpenSSH per-connection server daemon.
Dec 9 14:34:36 dns3 systemd[1]: Stopped OpenSSH per-connection server daemon.
Dec 9 14:34:36 dns3 systemd[1]: sshd@134-145.239.80.189:22-64.227.156.126:57278.service: Got no socket.
Dec 9 14:34:36 dns3 systemd[1]: sshd@134-145.239.80.189:22-64.227.156.126:57278.service: Failed to run 'start' task: Invalid argument
Dec 9 14:34:36 dns3 systemd[1]: sshd@134-145.239.80.189:22-64.227.156.126:57278.service: Failed with result 'resources'.