Re: Open Source Security Risks (was T3 Sues IBM To Break its Mainframe Monopoly)

2007-12-09 Thread David Cole
I think you have the open source security risks backwards, Herbie. One of the features of open source is that the source code is public. This means that ANYONE can read it, study it, find bugs in it, AND find trap doors in it! And "anyone" means anyone in the whole world! Thus, the risk of ma

Re: Open Source Security Risks (was T3 Sues IBM To Break its Mainframe Monopoly)

2007-12-10 Thread R.S.
David Cole wrote: I think you have the open source security risks backwards, Herbie. One of the features of open source is that the source code is public. This means that ANYONE can read it, study it, find bugs in it, AND find trap doors in it! And "anyone" means anyone in the whole world! O

Re: Open Source Security Risks (was T3 Sues IBM To Break its Mainframe Monopoly)

2007-12-10 Thread Clement Clarke
R.S. wrote: David Cole wrote: I think you have the open source security risks backwards, Herbie. One of the features of open source is that the source code is public. This means that ANYONE can read it, study it, find bugs in it, AND find trap doors in it! And "anyone" means anyone in the who

Re: Open Source Security Risks (was T3 Sues IBM To Break its Mainframe Monopoly)

2007-12-10 Thread Tom Marchant
On Mon, 10 Dec 2007 22:33:40 +0900, Clement Clarke wrote: > >You must agree that you will abide by the GNU terms, and not use it >commercially without some appreciation, or for war. What does that mean? -- Tom Marchant -- For I

Re: Open Source Security Risks (was T3 Sues IBM To Break its Mainframe Monopoly)

2007-12-17 Thread Jan MOEYERSONS
>One of the features of open source is that the source code is public. >This means that ANYONE can read it, study it, find bugs in it, AND >find trap doors in it! And "anyone" means anyone in the whole world! It really is a double-edged blade... Anyone can read it and find trap doors; true. But th