Re: Early heads-up: plan to remove local patches for TCP Wrappers support in sshd

Ed Maste <[email protected]>
Newsgroups gmane.os.freebsd.current,gmane.os.freebsd.security.general
Message-ID <CAPyFy2DZnHJDqsvFD_FzUz-hH9G5iVCbOb0UkELP5BWGn9KaSA@mail.gmail.com>
On Sat, 15 Feb 2020 at 05:03, Bjoern A. Zeeb
<[email protected]> wrote:
>
> I am also worried that the change will make a lot of machines
> unprotected upon updating to 13 if there is no big red warning flag
> before the install.

At least having sshd emit a warning is a prerequisite, certainly. I
don't yet know if there's a way via libwrap's API to determine if
rules are in place; there's a bit of investigation needed here still.

> I do understand the burden of maintaining a local patch (we lost the HA
> patches from base this way already).

Indeed. As you pointed out the libwrap patch is very small and easy to
review and reason about. My bigger concern is that libwrap is
essentially abandonware, and it has been dropped by just about
everyone else. As far as I know Debian is still patching libwrap
support into sshd but not anyone else.

It seems starting sshd from inetd via tcpd is a reasonable approach
for folks who want to use it; also, have folks using libwrap looked at
sshd's Match blocks to see if they provide the desired functionality?
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.