NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Security (Score:2)
Of course, the other side has its
Re:Security (Score:1)
That's a very good point. I'm certainly all for transparency in government and government software. It's also mentioned in the bill. Other people will likely cover that in their testimony and supporting documentation.
Is there a way to cover the auditability aspect of Open Source while discussing open standards and protocols? I'd like to stay within that narrow topic -- it helps to be laser-precise when talking to lawyers and legislators. :)
Re:Security (Score:2)
Diffie's argument revolves around a fundemental tenet of security: a secret is only as good as your ability to change it. For example, suppose you have a combination lock on the front door of the office. You may consider it secure because it cannot be cracked(!), and furthermore it is a closed, proprietary combination lock -- no one knows what goes on inside.
Now suppose you have 100 employees in your facility. Each and every one of them knows the combination. That's fine, because each and every one of them is trustworthy(!) and no one would squeal.
Now suppose your impenetrable combination lock gets cracked. What do you do? You can't change the combination because your 100 employees won't be able to get into the office anymore. Because you can't change your cracked combination, someone else who is not trustworthy can enter your building any time he wants without your permission, simply because you cannot change the combination.
Oh, and let's not forget that an untrustworthy cracker is unlikely to be afraid of breaking the law or even the Patriot act....
This analogy is the basis of Diffie's refutation of security by obscurity. A closed source package has its source code obscured. You cannot change it easily. It will have security holes -- every piece of software of value does. However, you cannot fix them -- only your vendor can fix them, and only on his timescale. Furthermore, because closed source software relies on a secret that cannot be easily changed (the binaries), it is fundementally insecure.
Open source, on the other hand, does not have this property. It is a secret that can be easily changed (much like a PGP key can be revoked and reissued). It is open to inspection, so it is more likely people will find security bugs. Furthermore, because it is easily changed, it is more likely to keep your secrets.
(I hope that makes some sense. It was early in the morning and Diffie was wandering pretty far afield when I heard him speak...)
Reply to This
Parent
Re:Security (Score:1)