l i n u x - u s e r s - g r o u p - o f - d a v i s
L U G O D
 
Next Meeting:
December 2: Social Gathering
Next Installfest:
TBA
Latest News:
Nov. 18: Officers elected
Page last updated:
2004 Mar 06 19:06
Events
 Meetings
 Installfests
 Demos
 Photos
Services
 Library
 LERT
 Jobs
 Documents
Interact
 Mailing Lists
 - Search
 - Archives
 Chat (IRC)
 Social Networks
About Us
 Members
 Projects
 Testimonials
 Call for Speakers
 Why Not MS?
 Finances
 Sponsors

^Home
?Search
?News & RSS
?Calendar
@Contact Us
$Buy Stuff
=Printable


The following is an archive of a post made to our 'vox mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox] Open Source and Security
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox] Open Source and Security



On Mon, Mar 01, 2004 at 12:10:39PM -0800, Byron Roberts wrote:
>  I feel like I'm totally missing something here....I thought that
> one of the big advantages of OSS was increased security, precisely
> because the code is accessible and able to be modified?  Or as a
> newbie is there some piece of information that I'm lacking?

Can't type much... only home for a bit, and bandwidth here is being drained by
a certain other person in the household, so it's a little hard to type into
SSH.

Anyway, while they may have a point when it comes to "not wanting to
touch someone else's old code" and so forth, that's really only ONE
opinion on the matter.  While one person may not want to mess with old
code, there'll most likely be someone ELSE somewhere in the world
who would be happy to.  Especially when compensation (e.g., money) is
involved.

In this case, though, the advantage Open Source has over closed source
is that there's no barrier -- technical (e.g., lack of access to source code)
or legal (e.g., copyrights and pattents) -- to getting things done.
(Changed, updated, bugfixed, etc.)

With closed-source, the barrier is immediate.  Example:

  "Hey Fred, OpenOffice.org seems to have a problem doing such-n-such"

     "Well I can try to fix it.  [pay me / I'm happy to help for free / etc.]"


Versus:

  "Hey Fred, Microsoft Office seems to have a problem doing such-n-such"

     "That sucks.  I hope they fix it and provide an update some day..."


In the first case, we assume Fred is interesting in helping, either for
compensation or not.  In the second case, it doesn't matter.  Nothing
you or Fred can do about it (except wait and hope).

If Fred was NOT interested, or lacked the technical skill or time,
even if you offered compensation, you're not stuck.  Just find
a suitable replacement for Fred.


Hoping this makes sense and kinda clears it up for you.

I'd be interested in seeing any other responses to the original CVBIG post.

-bill!
_______________________________________________
vox mailing list
vox@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox



LinkedIn
LUGOD Group on LinkedIn
facebook
LUGOD Group on Facebook

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
1105 Kennedy Place, Suite 1, Davis, CA 95616
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
nerdbooks.com
For numerous book donations.