Microsoft To Share Office Source Code
I_Love_Pocky! writes "According to this article, Microsoft is going to give its source code for Office 2003 to more than 30 different world governments. The purpose? So they can inspect the code for security flaws."
Interesting . . . wonder how long it will take to leak out of one of these offices and wind up on file sharing sites?
Only 30 eh? It doesn't mention anything about M.S. letting the US government see the code. Think they might still be a little bitter with that whole "You have a monopoly. We can't let you do that..." thing? Or do you think M.S. is afraid the Department of Homeland Security might issue another advisory saying that Office 2003 is insecure and everyone should switch to Open Office.
"Don't sweat the petty stuff and don't pet the sweaty stuff." -- by an Unknown Wise man.
Love this part:
Put identity in the browser.
The important questions is...
Is there a way for the governments to verify if the binaries that MS ships is from the same source that they are getting to see?
Will the governments be allowed to compile their own version ?
It's their new tactict to take over the world. First let governments look at their source, then once they use the source in something sue them. They are probably also hoping they will use the source in Open Source projects so they can get rid of them, the old kill two birds with one stone...
Good point, This offer should be rejected on many levels, first and foremost, shouldn't Microsoft be responsible for their own security.
Surely with a $500.00+ dollar pricetag for Office MS can afford to do their own homework !!
Alos, are any of these governments developing countries? Or southeast Asian? In other words is Microsoft entrusting the code to any governments that seem to take a blind eye to software piracy?
Well, if they compile these and they do not get the exact same binaries, they might claim they are cheating but as we know Microsoft, they will explain that their WC++ might not always produce the same output depending on many factors...
So, well, they have to believe it.
Trolling using another account since 2005.
When (not if) the source code is leaked, then how long will it be before MSFT claims that office code was integrated into OpenOffice. How much in royalties will they demand?
Ha, ha! Nobody ever says Italy.
If the government of a country has the source code of the software to examine for security flaws, doesn't this give MS a defense against liability from future lawsuits? For example, if the UK government gets to inspect the source code, continues to use MS-Office, and then has a major problem due to hackers hacking MS-Office; MS can say that the software was given a clean bill of health by the British government, so MS shouldn't be held liable.
I know that no defense is necessarily bulletproof, but this is just going to give MS's legal dept. more ammunition so that that MS can get away with writing sloppy code and not be found as grossly negligent.
* what is 'required' to agree beforehand with? ..and how will this agreement effect ones ability to work (with other 'source code(s)') in the future to come?
I don't claim I know more than I know, and if you know you know more than I know, then by all means, let me know.
If you cannot compile the given source to a fully working Microsoft Access (or whatever source is provided), how can you be sure that the program you buy from the store contains the same source code?
You can't, since you most likely can't compile the given source, and keep on using that compiled version!
This is just smoke and mirrors. Now Microsoft can say their code has been provided for auditing by some instance, so it's got to be safe. However, there is no guarantee that the defects found will be fixed at all, and that the fixes will ever be found in the actual product. There is also no guarantee that the software you obtain from the store is the same as that for which the source was provided.
You can easily implant backdoors to the supposedly "audited" source code: just don't give the newly modified source code with the backdoor back to auditing...
I do not moderate.
From the article (emphasis added by me)
The new initiative is an extension of Microsoft's Government Security Program, which allows the governments of more than 30 countries to examine most of Microsoft's underlying source code, or software blueprint for its flagship Windows operating system.
What's the benefit in looking at "Most of" the code and seeing if it is secure?
Absolutely nothing at all, apart from Microsoft getting an NDA signed on your behalf by your Govern(e)ment without any consultation with the public.
A pizza of radius z and thickness a has a volume of pi z z a
This still doesn't fix the problem of governements putting out documents in a closed format that limits who can use/view those documents. Sure there is the free MS Word Viewer, though that only says it supports MS Word 2000 and doesn't mention WinXP. So it may or may not work. Also, MS realeases these viewers a long time after the most recent version comes out, so the most recent viewer is usually a version or two behind the most recent MS Office Suite. I think all governments should stick with an open doc format like PDF. Any government can use an suite like OOo.org that will let them convert documents to PDF or even Flash.
If Tyranny and Oppression come to this land,
it will be in the guise of fighting a foreign enemy. -James Madison
I don't know about the rest of the world, but generally People Working At Governments aren't exactly the best and brightest or the best motivated workers. Let's call them Very Good at being Mediocre.
Imagine the following:
Boss: Jim, you're a programmer right?
Jim: uh, right
Boss: Management told me to inspect some code for bugs. I tossed it to the printer. Can you mark all the bugs with magic marker?
Exercise caution when modding this message up: the author acts like a jerk when his karma is excellent.
Microsoft is going to make sure that 30 governments have access to their source code so that they will know where the security flaws in Microsoft Office are. You have to ask yourself, what color hats are these people wearing? Why exactly would I want to use Office after this disclosure?
If developers who look at MS Office code are prhobited thereafter from working on other software projects such as open source projects that cross Office's domain, how many less contributers might there be to open source projects as a result of this?
Forget the legal recourse, just check the more shady BT repositories for the CD set because you KNOW someone's going to leak it out of spite. I give it a month after release before the "Office 2005 davelopers soarce kit pack" hits the streets on the pacific rim and a week more before it gets to middle eastern markets to be bought for 10 dinars by returning US servicemen/women.
CDs marked "Windows 99" were on the street in Bahrain and Saudi Arabia before I even bought my first win98 upgrade cd, and this probably won't be any different.
This is not nearly enough to satisfy governments. First of all, code that they don't compile themselves is not guaranteed to stem from the same set of sources. Second, the source code to the OS, and to the compilers is needed as well, because, hey, what does that black box kernel, dll, or compiler toolkit add to the pristine source?
Responsible governments would either avoid closed-source products completely, or they should require a complete source code system that they could bootstrap themselves. No hidden binary at all!
Would Microsoft provide such a complete, source code system that could bootstrap itself? It was reported many times earlier that they are having a helluvatime to maintain their own compiling environment. Would they be able to package it in such a way that non-Microsoft personnel could do something with it...
... assuming that they were sincere, and not just pulling a cheap PR stunt?
cpghost at Cordula's Web.
The bottom line is that they will never see all of the source, so there is no way to verify that lower level DLLs don't have security issues/backdoors.
This entire 'handout' from MS is nothing more than a ploy to taint those reviewers, and to hopefully lock those governments into MS.
You are being MICROattacked, from various angles, in a SOFT manner.
Is Microsoft hoping that they can kill more open source by making copyrighted code available? Do they hope they will then find it in something like OpenOffice.org or AbiWord so they can sue those projects into non-existence?
If that's the case, how is this possible? ...
Nothing is truly original. Writing an original program is the result of taking ideas from other people's work, and putting them together in a different way.
Here's a story: Some talented and enthusiastic programmer (like I hope to be) from viewing Microsoft's "shared" code and saying to himself "Oh... That's how they do that.". Then this person closes the Microsoft code, never to look at it again, and makes some new changes to the code in OpenOffice.org based on his experience and understanding of all of the code that he has read and learned from in the past.
Can Microsoft now sue this person?
If so, Brian Kernighan and Dennis Richie have one Hell of a Payday coming from their lawsuit.
A couple of years ago, I was at Defcon. A Russian gentleman started his talk, when he was interrupted by the man who organizes Defcon. The speaker was asked to say "nuclear wessels". The speaker was clearly confused by the request, but the organizer persisted. I doubt the speaker knew what he was saying: he was working from a script that he'd prepared before, and obviously was not able to speak conversational English, let alone understand "nuclear wessels". Finally, after much prodding, the speaker said "nuclear wessels" into the mic, with a very confused expression on his face. The organizer sat down and the talk began.
The next day, that speaker was arrested. I keep wondering if he considered that the two events were somehow related.
Of course, now we all know that Dmitri was in fact arrested for a DMCA violation, but until somebody explained that to him...