1 |
One reason I can think of is to keep it simple across platforms. |
2 |
tcpd is, in general OS non-specific. When you need to make security |
3 |
suggestions that span platforms (Linux, Solaris, BSD, etc) this is what |
4 |
you want. You can install tcpd on all platforms, and the configuration |
5 |
is the same. |
6 |
|
7 |
iptables is Linux specific. To create the same functionallity on other |
8 |
platforms, you will be stuck with several different packages and config |
9 |
files to provide the same functionallity. This can become hard to manage |
10 |
very quickly. |
11 |
|
12 |
|
13 |
|
14 |
.------[ Peter Volkov wrote (2005/10/13 at 12:32:05 AM) ]------ |
15 |
| |
16 |
> Hello. |
17 |
> |
18 |
> Can anybody explain the differences, pro/con between the mentioned two |
19 |
> approaches in the subject? |
20 |
> |
21 |
> I thought that fewer programs I have on my server the more secure it is. |
22 |
> But gentoo security guide and some people on this list suggest usage of |
23 |
> hosts.allow, hosts.deny files, which only work if I have tpcd installed, |
24 |
> thus another service which weaken server's security. But normaly each |
25 |
> server has iptables installed. So every sysadmin can obtain hosts.allow, |
26 |
> hosts.deny functionality with simple iptables rule like the following: |
27 |
> |
28 |
> iptables -A INPUT -s bad_host -j DROP |
29 |
> |
30 |
> This is the base functionality of iptables. No PoM is nescesary for such |
31 |
> kind of things. |
32 |
> |
33 |
> More. I think some portable bash script that will parse host.* files and |
34 |
> create iptables rules is very simple to write! |
35 |
> |
36 |
> So why many people and security guides still suggest the use of tcpd |
37 |
> over simple iptables rules? |
38 |
> |
39 |
> Thank you for your time, |
40 |
> Peter. |
41 |
|
42 |
|
43 |
| |
44 |
`^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
45 |
|
46 |
|
47 |
-- |
48 |
-- |
49 |
gentoo-security@g.o mailing list |