Google To Microsoft — Give Users Choices In Vista

An anonymous reader writes "A Google spokesman has asked Microsoft to 'preserve user choice for search and other applications' with its future products, such as Vista. The spokesman made this comment after meeting with European Union antitrust regulators, though he added that at this point, the company has no plans to make antitrust allegations against Redmond. Notably, McAfee and Symantec have accused Microsoft of not being forthcoming with the code they need to ensure their security wares run smoothly on Vista, and the EU has already expressed concern about Microsoft's potentially anticompetitive plans."

No sympathy for McAfee and Symantec

[Anonymous Coward]

Why should Microsoft have to maintain broken code just to preserve McAfee and Symantec revenue streams? That's like saying that, say, Ford shouldn't redesign defective brakes on their cars because it would hurt the sales of aftermarket brake parts.

I'd care more if...

[rainman_bc]

If McAfee and Norton didn't make products that suck resources real bad. If ever there was a product that could be called bloatware, those two are it. Give me Trend AV any day thanks.

Then again I'm on my Linux laptop running no AV software.

Re:No sympathy for McAfee and Symantec

[Wheatfieldcrows]

You may be over simplifying, they didn't ask Microsoft to maintain broken code. They just asked MS to reveal the Windows code they need to make it easier to write a compatible AV program. It's like designing a new engine and then not telling anyone the size of the bolts you used so they can't make simple bolt on aftermarket parts

Re:No sympathy for McAfee and Symantec

[Chosen Reject]

I don't think you understand. McAfee and Symantec aren't complaining that Vista is better and more secure. They're complaint is that Microsoft won't give them the API to low level kernel stuff so that they can detect viruses, while at the same time, Microsoft is going to use that same API for their own virus detection. This isn't Ford continuing to make defective brakes so that third-party brake manufacturers can still be in business, this is Ford some how magically making the brake design unknown to anyone else in the world so that only Ford can make brake replacements. Though in a physical world I don't know how they would do that. This is only possible in software.

This is getting ridiculous...

[X-treme-LLama]

Is there anyone else who thinks it's a little unfair for Microsoft to criticized for cutting out Symantec, etc. They've been railed for years on their complete lack of security focus, probably nowhere more than here. They're finally attempting to fill that need (admittedly in microsoft fashion), and now it's unfair to AV software makers? C'mon Symantec and others built their business around securing an insecure OS, it's not the OS's fault for finally working to secure itself. Sure MS could open up more of their code to allow AV software to get around their own security and AV solutions, but why should they.

I guess I don't understand why it's MS's job to make it easier for other software makers. If they want to market their software they should employ some programmers who are smart enough to code around MS. As long as MS isn't actively disabling competitors software I don't see why this is their fault..

We wanted them to be more secure in the first place!!!

And just so no one thinks I'm a fanboy, I'm typing this from a Mac :) -- I'm just against BS in general and against bitching at Microsoft just because it's Microsoft..

Re:This is getting ridiculous...

[orasio]

Te issue is that they are a monopoly right now.
Monopolists don't have the same rights than other people.
So they can't do what others can.
One thing is this: using their OS monopoly to impose their AV solution.
That is anti-competitive. You might say that it's not fair, but when you are talking about monopolies, the meaning of fairness changes, because they don't compete under the same conditions.

Re:I'd care more if...

[Shadow99_1]

*cough* Anti-MS Zealot *cough*

Other AV's work just fine without these tools Symantec and McAfee demand. This is not an issue of MS crowding out a critical component from potential competitors to take market share. This is MS making an attempt to do what they promised (ie secure windows more than they have in the past). Whether I agree with the method MS is taking or not, this has more to do with Symantec and McAfee being whiny brats that refuse to give up 'control' of 'security' to the ones who should have been doign that job in the first place. The compnent they want access to is the layer that provides basic system protection and notification to the user about the systems staus, so they can use their own interface on it with whatever they decide is important to be their. I don't trust either side to really get it right, but at least in this I don't see any point what so ever to allow the other companies access where they really don't need to be. This will not make people more secure, this is about McAfee and Symantec having to face reality that certain parts of the system don't function like they used to and whining all over the place that they changed things is stupid.

Re:No sympathy for McAfee and Symantec

[PsychicX]

while at the same time, Microsoft is going to use that same API for their own virus detection

Is there any evidence that this is actually true? The things I know are:

• The new Microsoft guideline thingies say, no using undocumented or non-public APIs.
• The kernel and low level system guys gets pretty angry when software uses undocumented functionality. That stuff is undocumented precisely because it's not intended to be used.
• Windows Defender, like any other program, is easy to analyze. Determining a complete list of APIs that it uses would be easy using existing tools and techniques, and use of undocumented APIs could be trivially uncovered.
• The only way the MS guys could actually lock out anybody except themselves would be to hardcode a hash of the Defender exe inside the kernel or something. This is another thing that would show up under analysis (though more complex than the previous point). And they couldn't really do that, since it'd make patching Defender kind of hellish. And simply checking executable name would be no good, of course.

So, I guess it just strikes me as extremely unlikely that Microsoft is using undocumented APIs that nobody else knows about or has access to. People -- and by "people" I mean major products from major corporations -- have used undocumented APIs frequently in the past just because they happened to find something that sounded handy in the various DLL export tables. Microsoft using APIs but not allowing access to anyone else sounds pretty good, but I've yet to see any actual evidence to support the claim.

So I ask again. Where is this claim validated?