I am no expert in open and closed sources, programing language, communities, etc. - but I am in government and one of the biggest concerns is (or should be) security.
1) Is open source really as secure as closed systems, or does it seem more secure because many of the hackers play with what a majority of the average Joe's use?
2) Is not open source.. well...open? If you are waiting on the general community to solve your problem, isn't it because everyone has the source codes to help you fix the problem? If they have the source codes, does it not make things easier to hack? With mention of the FBI, Wall Street banking, etc. using open source I might be off base on this, but maybe someone can explain it on simple terms to me. Why would an open source code be safe? If it is just algorithms that are used for security, is that not the same as what closed sources use?
3) In my years of experience working in government, almost ten, the most difficult thing regarding computers is the lack of IT staff and money for program updates. Only two years ago we stopped using a DOS program developed by a former employee 15 years previous. It is not secure and not even year 2000 compliant (We enter 21 for 2001). We still have to keep this division database and use it because no one seems to know how to transfer the data into some program more recent and the data is important. Knowing this, I am sure you can understand that we don't change IE, Word, Outlook, etc. when new versions are released, not to say the updates. IT has a difficult time just keeping the stations up and functioning. With that in mind, open systems look attractive because the operating systems are free and many of the programs you want already come with the operating system. Of course, even open systems have updates and if government does not do them now, I doubt they will in the future.
So which, in this type environment, is most secure - an open or closed source system?
Discussion on:
Message 14 of 1
The best of ZDNet, delivered
ZDNet Newsletters
Get the best of ZDNet delivered straight to your inbox
