Linux server as it own firewall
From: James Puckett (jpuckett@ticom.com)Date: 09/12/01
- Previous message: Vinicius Dalesandro: "How to share a listening NetCat server"
- Next in thread: Ross Vandegrift: "Re: Linux server as it own firewall"
- Reply: Ross Vandegrift: "Re: Linux server as it own firewall"
- Reply: Brian Cervenka: "Re: FW: Linux server as it own firewall"
- Reply: Mark Ryback: "Re: Linux server as it own firewall"
- Reply: Glenn H English: "Re: Linux server as it own firewall"
- Reply: Mogens Valentin: "Re: Linux server as it own firewall"
- Reply: Mark Rafn: "Re: Linux server as it own firewall"
- Reply: Ross Del Duca: "Re: Linux server as it own firewall"
- Reply: Rob 'Feztaa' Park: "Re: Linux server as it own firewall"
- Reply: Seth Arnold: "Re: Linux server as it own firewall"
- Reply: Scott Gifford: "Re: Linux server as it own firewall"
- Reply: Scott Gifford: "Re: Fw: Re[2]: FW: Linux server as it own firewall"
- Reply: Scott Gifford: "Re: Fw: Re[2]: FW: Linux server as it own firewall"
- Reply: Jeff Schaller: "Re: Fw: Re[2]: FW: Linux server as it own firewall"
- Reply: Zow: "Re: Fw: Re[2]: FW: Linux server as it own firewall"
- Reply: Jeff Schaller: "Re: Fw: Re[2]: FW: Linux server as it own firewall"
- Reply: Momchil Velikov: "Re: Fw: Re[2]: FW: Linux server as it own firewall"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: James Puckett <jpuckett@ticom.com> To: focus-linux@securityfocus.com Subject: Linux server as it own firewall Date: Wed, 12 Sep 2001 13:25:21 -0400 Message-Id: <0109121325210B.19384@blackwell>
All,
I am considering having the firewall for a Linux server I am building
running on the server itself using IPTables. This server will see very little
load, so performance will probably not be an issue. What I am wondering is,
what are the implications of having a Linux box on the internet running its
own firewall? The way I see it, if someone can manage to break into a locked
down firewall, he will not have too many problems getting into the machines
behind the firewall. On the other hand, if the attacks take a while to go
off, the extra time it takes to get into the server behind the FW could be
what saves the server if the intrusion is detected. I also wonder about the
obvious problem of having extra daemons on the firewall adding to the number
of exploitable holes on one machine.
Overall I am really against the idea, but in the long run working this way
could save some money, and if it looks like the system won't be made too
insecure this could be a viable idea.
Thoughts,
Thanks
-james
- Previous message: Vinicius Dalesandro: "How to share a listening NetCat server"
- Next in thread: Ross Vandegrift: "Re: Linux server as it own firewall"
- Reply: Ross Vandegrift: "Re: Linux server as it own firewall"
- Reply: Brian Cervenka: "Re: FW: Linux server as it own firewall"
- Reply: Mark Ryback: "Re: Linux server as it own firewall"
- Reply: Glenn H English: "Re: Linux server as it own firewall"
- Reply: Mogens Valentin: "Re: Linux server as it own firewall"
- Reply: Mark Rafn: "Re: Linux server as it own firewall"
- Reply: Ross Del Duca: "Re: Linux server as it own firewall"
- Reply: Rob 'Feztaa' Park: "Re: Linux server as it own firewall"
- Reply: Seth Arnold: "Re: Linux server as it own firewall"
- Reply: Scott Gifford: "Re: Linux server as it own firewall"
- Reply: Scott Gifford: "Re: Fw: Re[2]: FW: Linux server as it own firewall"
- Reply: Scott Gifford: "Re: Fw: Re[2]: FW: Linux server as it own firewall"
- Reply: Jeff Schaller: "Re: Fw: Re[2]: FW: Linux server as it own firewall"
- Reply: Zow: "Re: Fw: Re[2]: FW: Linux server as it own firewall"
- Reply: Jeff Schaller: "Re: Fw: Re[2]: FW: Linux server as it own firewall"
- Reply: Momchil Velikov: "Re: Fw: Re[2]: FW: Linux server as it own firewall"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|