Feeds

DoJ brown-noses MS further in revised settlement

The large print giveth and the small print taketh away

  • alert
  • submit to reddit

Internet Security Threat Report 2014

Proposed settlement terms for the largest anti-trust defendant since Ma Bell have been tightened up a bit since a draft came out last week, but important exceptions remain.

Showy pro-consumer language now flows around the numerous exceptions, as if written not by the DoJ, but by the MS marketing department.

No more restrictions on dual-boot OEM machines. No more restrictions on outside middleware. And all MS middleware has got to be easily uninstallable by end users, via the Add/Remove function in Control Panel, for example.

That sounds great. Except that,

"the Windows Operating System Product may invoke a Microsoft Middleware Product in any instance in which: 1. that Microsoft Middleware Product would be invoked solely for use in inter-operating with a server maintained by Microsoft (outside the context of general Web browsing)...."

And that might mean you can't remove Internet Explorer because you need all those crucial product updates, and surely we wouldn't want some sketchy other-worldly browser connecting to the pristine MS servers. The company can claim that enhanced security features in its product make it unwise to use another. A bit of a stretch, surely, but they've stretched things at least that far many times before.

But let's read a bit further:

"....or 2. that designated Non-Microsoft Middleware Product fails to implement a reasonable technical requirement (e.g., a requirement to be able to host a particular ActiveX control) that is necessary for valid technical reasons to supply the end user with functionality consistent with a Windows Operating System Product, provided that the technical reasons are described in a reasonably prompt manner to any ISV that requests them."

Since when are ActiveX controls a 'reasonable technical requirement'? One can easily imagine difficulty employing an e-mail client less likely to flood you with malicious HTML messages than Outlook, for example. (OK, Outlook insecurity is a pet peeve of mine; but in fact, the sky's the limit in applying this sweet little exception.)

And as we reported earlier, virtually any API can be withheld on the pretext that releasing it could endanger security, third-party secrets, or DRM schemes.

"No provision of this Final Judgment shall: 1. Require Microsoft to document, disclose or license to third parties: (a) portions of APIs or Documentation or portions or layers of Communications Protocols the disclosure of which would compromise the security of a particular installation or group of installations of anti-piracy, anti-virus, software licensing, digital rights management, encryption or authentication systems, including without limitation, keys, authorization tokens or enforcement criteria; or (b) any API, interface or other information related to any Microsoft product if lawfully directed not to do so by a governmental agency of competent jurisdiction.

And guess who's been nominated arbiter of who can and can't be trusted with this data. Why, it can be withheld from anyone who fails to:

"meet[] reasonable, objective standards established by Microsoft for certifying the authenticity and viability of its business, (d) agree[] to submit, at its own expense, any computer program using such APIs, Documentation or Communication Protocols to third-party verification, approved by Microsoft, to test for and ensure verification and compliance with Microsoft specifications for use of the API or interface."

So what we have here are a few light cosmetic changes in the phrasing to reinforce the illusion of victory for consumers, OEMs and competitors, most likely to save face for a compliant DoJ, and to make the language more palatable and euphemistic in keeping with MS marketing conventions.

From that perspective it's a win/win situation. ®

Related Stories

MS snags crucial authentication, DRM opt-outs in DoJ settlement
All you ever wanted to know about the DoJ's Windows cave in

Internet Security Threat Report 2014

More from The Register

next story
Euro Parliament VOTES to BREAK UP GOOGLE. Er, OK then
It CANNA do it, captain.They DON'T have the POWER!
Download alert: Nearly ALL top 100 Android, iOS paid apps hacked
Attack of the Clones? Yeah, but much, much scarier – report
NSA SOURCE CODE LEAK: Information slurp tools to appear online
Now you can run your own intelligence agency
Post-Microsoft, post-PC programming: The portable REVOLUTION
Code jockeys: count up and grab your fabulous tablets
Twitter App Graph exposes smartphone spyware feature
You don't want everyone to compile app lists from your fondleware? BAD LUCK
Microsoft adds video offering to Office 365. Oh NOES, you'll need Adobe Flash
Lovely presentations... but not on your Flash-hating mobe
prev story

Whitepapers

10 ways wire data helps conquer IT complexity
IT teams can automatically detect problems across the IT environment, spot data theft, select unique pieces of transaction payloads to send to a data source, and more.
Getting started with customer-focused identity management
Learn why identity is a fundamental requirement to digital growth, and how without it there is no way to identify and engage customers in a meaningful way.
How to determine if cloud backup is right for your servers
Two key factors, technical feasibility and TCO economics, that backup and IT operations managers should consider when assessing cloud backup.
Reg Reader Research: SaaS based Email and Office Productivity Tools
Read this Reg reader report which provides advice and guidance for SMBs towards the use of SaaS based email and Office productivity tools.
Mitigating web security risk with SSL certificates
Web-based systems are essential tools for running business processes and delivering services to customers.