right, but you can still check wh's doing what and try to find them without "telling them". I mean, just block the port and log the attempts. the problem with the approach of trying to keep them connected to have more time to discover them is that nothing guarantees you'll trace them, and you have to check and recheck the code to make sure there is no hole in it. similar stuff has been discussed by cheswick&co in "builing internet firewalls" I think. there they talk about the risks they've taking trying to get the attacker (nd they also talk about risks that may be created by the use of safe-finger stuff....). - [To unsubscribe, send mail to [EMAIL PROTECTED] with "unsubscribe firewalls" in the body of the message.]
- FW: Redirecting closed port connections Eddy Kalem
- Re: FW: Redirecting closed port connections parks
- Re: FW: Redirecting closed port connections parks
- RE: FW: Redirecting closed port connections William . Stackpole
- RE: FW: Redirecting closed port connections mouss
- RE: FW: Redirecting closed port connections Paul D. Robertson
- RE: FW: Redirecting closed port connections William . Stackpole
- RE: FW: Redirecting closed port connections mouss
- RE: FW: Redirecting closed port connections Paul D. Robertson
- RE: FW: Redirecting closed port connections Ben Nagy
- RE: FW: Redirecting closed port connections William . Stackpole
- RE: FW: Redirecting closed port connections Damian Gerow
- RE: FW: Redirecting closed port connections mouss
- SOS: VPN Thru Linux RedHat 6.1 as gateway Rajesh Divakaran
- Re: FW: Redirecting closed port connections Steve Coleman
