Sorry, but openssh no longer supports tcp-wrappers, and it seems like
you're trying to use it.  Update your ${EROOT}/etc/hosts.{allow,deny} please.
Running the full OpenSSH testsuite requires a usable shell for the 'portage'
user, so we will run a subset only.
After upgrading to openssh-8.2p1 please restart sshd, otherwise you
will not be able to establish new sessions. Restarting sshd over a ssh
connection is generally safe.
From openssh-9.2_p1-r1 the supplied systemd unit file defaults to
'Restart=on-failure', which causes the service to automatically restart if it
terminates with an unclean exit code or signal. This feature is useful for most users,
but it can increase the vulnerability of the system in the event of a future exploit.
If you have a web-facing setup or are concerned about security, it is recommended to
set 'Restart=no' in your sshd unit file.

Sorry, but openssh no longer supports tcp-wrappers, and it seems like
you're trying to use it.  Update your ${EROOT}/etc/hosts.{allow,deny} please.
Running the full OpenSSH testsuite requires a usable shell for the 'portage'
user, so we will run a subset only.
After upgrading to openssh-8.2p1 please restart sshd, otherwise you
will not be able to establish new sessions. Restarting sshd over a ssh
connection is generally safe.
From openssh-9.2_p1-r1 the supplied systemd unit file defaults to
'Restart=on-failure', which causes the service to automatically restart if it
terminates with an unclean exit code or signal. This feature is useful for most users,
but it can increase the vulnerability of the system in the event of a future exploit.
If you have a web-facing setup or are concerned about security, it is recommended to
set 'Restart=no' in your sshd unit file.