
implemented any of the above steps yet, now is a good time to take a break, go back to the top, and have at it.
The most important steps are the ones above.
A few quick conclusions...
"What is best iptables, ipchains, tcpwrappers, or portsentry?" The quick answer is that iptables can do more
than any of the others. So if you are using a 2.4 kernel, use iptables. Then, ipchains if using a 2.2 kernel. The
long answer is "it just depends on what you are doing and what the objective is". Sorry. The other tools all
have some merit in any given situation, and all can be effective in the right situation.
"Do I really need all these packages?" No, but please combine more than one approach, and please follow all
the above recommendations. iptables by itself is good, but in conjunction with some of the other approaches,
we are even stronger. Do not rely on any single mechanism to provide a security blanket. "Layers" of
protection is always best. As is sound administrative practices. The best iptables script in the world is but one
piece of the puzzle, and should not be used to hide other system weaknesses.
"If I have a small home LAN, do I need to have a firewall on each computer?" No, not necessary as long as
the LAN gateway has a properly configured firewall. Unwanted traffic should be stopped at that point. And
as long as this is working as intended, there should be no unwanted traffic on the LAN. But, by the same
token, doing this certainly does no harm. And on larger LANs that might be mixed platform, or with
untrusted users, it would be advisable.
Security Quick−Start HOWTO for Red Hat Linux
5.9. Where to Start 35
Commenti su questo manuale