Hello Glen, Why don't you firewall the box itself ?
1) My server runs its own firewalling and I havn't had a problem. 2) I think this was a problem with the Service Provider - Use something like ipchains/iptables and ipfwadm (masq. back into network) - where you have control 3) Now you do :) 4) No, but it does limit the chances (greatly). Why open something that you don't want like SNMP for public query ? 5) No. You can make the machine connect to any port on any server and get traffic from them, without them beeing able to setup a connection to you. Here is the ipchains code to do that (set your policy to deny) $EXTIP="your external ip" ipchains -A output -p tcp -s $EXTIP -d $ANY -j ACCEPT ipchains -A input -p tcp -y ! -s $ANY -d $EXTIP -j ACCEPT If this is a true firewall (i.e. dedicate) then you can even use masq. Just my 2c Cheers, Pieter -----Original Message----- From: Glen Lee Edwards [mailto:[EMAIL PROTECTED]] Sent: 06 May 2002 08:06 To: [EMAIL PROTECTED] Subject: Re: Hacked again... Pieter De Wit writes: >Hello Original Poster, > >Sorry I joined the thread late, but why don't you firewall the box(es) using >ipchains or iptables ? I haven't done that for several reasons: 1) If the firewall box goes down, the entire system goes down. 2) I had a leased server that was behind a firewall. It frequently was a pain to deal with. 3) Until recently I haven't needed to. 4) Putting in a firewall doesn't guarantee that you won't be hacked. The first time I was hacked the box in question was behind a firewall. The jerk was still able to gain root access. 5) Having a tight firewall is like living in a fenced in yard. No one can get in, but you can't get out. I have no desire to live on an island. Glen _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
