Firewall Wizards mailing list archives
Re: Penetration testing via shrinkware
From: "Stephen P. Berry" <spb () incyte com>
Date: Wed, 23 Sep 1998 18:15:33 -0700
-----BEGIN PGP SIGNED MESSAGE-----
What does this mish-mash of observations tell us? Nothing new. The art of software development is still in its childhood. Programmers abound, but software engineers - or programmers who use a software engineering approach - are few and far between. There is no method that is "foolproof"; and if one existed, it probably wouldn't be "damfoolproof". Peer review is wonderful, but first you need (a) something against which to review (specifications? design?), (b) perhaps a methodology, (c) certainly a methodological approach, and (d) probably some talent.
And of course all of this doesn't just apply to software development but more generally to all fields related to the design, implimentation and review of network security applications.
And formal proofs are behind even that curve.
This is another one of those moments when I think there ought to be two separate lists: firewalls-theory and firewalls-practice. To tell the truth, even if there was a schema for formally proving a system secure (mod whatever process definition of `secure' the schema posits), I would remain unconvinced of the real-world utility of such a proof, excepting the possible placebo effect on The Mgmt. Okay, _ceteris paribus_ it would be nice to know that one box was provably `secure' whereas some other box is not. But what does this actually tell us? It tells me the same thing when the provably `secure' whatsit is a firewall as when the whatsit is a cryptosystem---the weak spot is going to be between the ears or in the pressure-points of the folks at either end. Put another way, you could probably better improve the security of computer systems in general by burning all PostIt notes than by eliminating all software bugs. Well, that's probably a little too fortune(6)-ish to be absolutely true, but you get the idea. - -Steve -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNgmc1irw2ePTkM9BAQHUCAP8DKnY3XOscKrAdPBJEi0HSdegPz8+ELYC ERL49/P+v/f+MDnZ4JqOpzS5g8SYSqmZOnw9WHyJW8swnK2JCFJfzopsqnY/DZKX X4mA81M3zvC/0FFcHBgsam7MtTz839ZHTivMqFBgu5uEi28c/ZPvnKcSQZLYq3bZ Q9lHD0QkS2U= =xMYq -----END PGP SIGNATURE-----
Current thread:
- Re: Penetration testing via shrinkware, (continued)
- Re: Penetration testing via shrinkware Paul D. Robertson (Sep 20)
- Re: Penetration testing via shrinkware John McDermott (Sep 19)
- Re: Penetration testing via shrinkware Paul D. Robertson (Sep 20)
- Re: Penetration testing via shrinkware Marcus J. Ranum (Sep 21)
- Re: Penetration testing via shrinkware Paul D. Robertson (Sep 21)
- Re: Penetration testing via shrinkware Ted Doty (Sep 21)
- Re: Penetration testing via shrinkware Paul D. Robertson (Sep 21)
- Re: Penetration testing via shrinkware Darren Reed (Sep 22)
- Re: Penetration testing via shrinkware Ted Doty (Sep 22)
- Re: Penetration testing via shrinkware Paul D. Robertson (Sep 20)
- Re: Penetration testing via shrinkware Joseph S. D. Yao (Sep 22)
- Re: Penetration testing via shrinkware Stephen P. Berry (Sep 24)
- Re: Penetration testing via shrinkware tqbf (Sep 21)
- Re: Penetration testing via shrinkware Marcus J. Ranum (Sep 20)
- Re: Penetration testing via shrinkware Joseph S. D. Yao (Sep 21)
- Re: Penetration testing via shrinkware Paul D. Robertson (Sep 20)
- Re: Penetration testing via shrinkware Marcus J. Ranum (Sep 20)
- Re: Penetration testing via shrinkware Christopher Nicholls (Sep 21)