Date: Mon, 28 Oct 2024 17:41:59 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 280440] security/openssh-portable: tcpwrappers no longer works with spawning processes Message-ID: <bug-280440-7788-5mITJBrEma@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-280440-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-280440-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D280440 --- Comment #5 from mike@sentex.net --- Note, For my use case I worked around the issue. I had a few customers where geofencing was a requirement and hooked in ACLs another way that actually is much more flexible. However, I would not be surprised if I was the last per= son on the planet using tcp_wrappers to make use of this old feature. I think = the redesign to separate ssh sessions broke the previous patch, so more work th= an a few tweaks are probably needed. If someone wants to close the ticket and j= ust declare tcp_wrappers no longer supported fully, I would be fine with it.=20 [1] I have a small golang daemon listening in on pflog0 looking for a provi= ded pf rule match. It then hands the IP off to a shell script that decides on a number of criteria (country, reputation list etc) and either does nothing or adds the IP to a block table and kills the existing state. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-280440-7788-5mITJBrEma>