Open Source Security Bugs Uncovered

[James Sissel]

And remember, this is exactly why the code is open.  Open does not mean free of bugs.  Open means people can look at the code and find the bugs ... if they wish.  As opposed to closed where you can't look at the code, can't find the bugs, can't decide if the code is secure for you to use, etc.  "Just trust us", says Micro$oft.

Billy Crook <billycrook at gmail.com> wrote:  I think the numbers really speak for themselves. While this article
may have been written to scare people, I'm proud to see that libre
software authors can write nearly half a million lines of code for
gratis, and make less than three hundred mistakes. ...Three hundred
mistakes which took the DHS, and Stanford University, and some
faceless corporation some two years, and $300,000 to find. And the
vast majority have already been fixed.

I think this makes FLOSS look incredibly secure.

On Jan 11, 2008 1:22 PM, Julie wrote:
> Read about it here:
>
> http://www.pcworld.com/businesscenter/article/141226/open_source_security_bugs_uncovered.html
>
> What do you all think about this?
>
> Julie @};-
>
>
> ________________________________
> Never miss a thing. Make Yahoo your homepage.
> _______________________________________________
> Kclug mailing list
> Kclug at kclug.org
> http://kclug.org/mailman/listinfo/kclug
>
>
_______________________________________________
Kclug mailing list
Kclug at kclug.org
http://kclug.org/mailman/listinfo/kclug

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kclug.org/pipermail/kclug/attachments/20080111/02b36eb3/attachment.htm