Re: checkpoint firewall -1 sp3
From: Greg Hennessy (spamcatcher@example.com)
Date: 02/15/03
- Next message: chrisclu: "Re: Outpost Firewall"
- Previous message: B. Switzer: "Re: checkpoint firewall -1 sp3"
- In reply to: B. Switzer: "Re: checkpoint firewall -1 sp3"
- Next in thread: B. Switzer: "Re: checkpoint firewall -1 sp3"
- Reply: B. Switzer: "Re: checkpoint firewall -1 sp3"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: Greg Hennessy <spamcatcher@example.com> Date: Sat, 15 Feb 2003 19:19:56 +0000
On Sat, 15 Feb 2003 14:13:27 -0500, "B. Switzer" <bswitzer@myprivacy.ca>
wrote:
>And what would break?
Anything that exploits a weakness or bug in the software I would consider a
break.
>
>'if something breaks' is a somewhat specious argument.
Thats fine until you have a pressing need to run a new business critical
service through the firewall and one finds that it doesnt work.
>But if the box is doing what you need it to do, then why continually pay
>through the nose? You bought the software, it's yours to use, and presumably
>the most significant bugs were discovered and fixed within your update
>period, however long that might be.
If one doesnt intend to ever change a running security policy and have all
services set in a***, then such an approach would have merit.
greg
-- $ReplyAddress =~ s#\@.*$##; # Delete everything after the '@' There's fighting on the left and marching on the right Don't look up in the sky you're gonna die of fright
- Next message: chrisclu: "Re: Outpost Firewall"
- Previous message: B. Switzer: "Re: checkpoint firewall -1 sp3"
- In reply to: B. Switzer: "Re: checkpoint firewall -1 sp3"
- Next in thread: B. Switzer: "Re: checkpoint firewall -1 sp3"
- Reply: B. Switzer: "Re: checkpoint firewall -1 sp3"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]