Carlos E. R. wrote:
On 2016-11-14 01:22, Lew Wolfgang wrote:
On 11/13/2016 01:21 PM, Carlos E. R. wrote:
On 2016-11-13 22:10, Dave Howorth wrote:
I remember reading that tcpwrappers is now deprecated. There are apparently vastly superior ways to control remote access these days. It's well known that iptables is much easier to understand and configure safely than hosts.allow and hosts.deny. I'm also sure that systemd has various target files somewhere that can also serve. After all, why should we continue to use a capability that has been serving us well for 20 and more years when there are new shiny things hanging about to occupy our attention? (do I need a smiley?)
The problem is, what are those new things?
I'm not proficient enough on Iptables to write my own rules, I use SuSEfirewall2 instead. How would I create entries in that file equivalent to host.allow/deny entries?
I'm not proficient with SuSEfirewall2, iptables is much easier I find :-) For my purposes, one or more of these would do: iptables -A INPUT -p tcp -i ethx --dport 873 i-s badclient -j REJECT I would just prefer to keep this sort of silly crud "close" to the app having the problem, not in the firewall. -- Per Jessen, Zürich (1.9°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org