Summary of MS unDRM "Bad" Patches Needed

[ron spencer]

given the length of the threads on unDRM and FairUse4WM program, could we get a sticky or something as to what Micr*soft Updates (KBs) NOT to install...it is sometimes hard to find in threads of a few hundred. A summary is always nice.

thanks

[josh2]

As of now I don't think they've released any KB patches to patch FairUse4WM.. they have thus far only pushed them with new individualizations.

Josh

[protectyoursources]

Microsoft requires the content service providers to push the individualisations out to thier customers ...

Subject: Notification: WMDRM Circumvention Patch Available

MICROSOFT CONFIDENTIAL

This email provides information about Microsoft's technical response to the FairUse4WM circumvention tool that is currently circulating on various Internet sites, which decrypts content protected by WMDRM. On September 19th, 2006, Microsoft released a new update to the Individualized Blackbox component (IBX) which thwarts all currently known versions of the FairUse4WM circumvention tool.

Supported platforms at this time include Windows Media Format SDK 9.5 and Windows Media Format SDK 11 Beta 2 on Windows XP, as well as the version of Windows Media Format SDK 11 that ships with Windows Vista Release Candidate 1. This update is not yet available for the Windows Media Format 9 Series FSDK or for users of Windows XP Media Center Edition 2005 Update Rollup 2. Users of Windows XP Media Center Edition 2005 Update Rollup 2 can be encouraged to download and install Windows Media Player 11 Beta 2, which is compatible with these robustness updates.

Partner feedback from our previous release was that it was important that we increment the Security Version of the IBX, allowing them to detect the presence of the update remotely. The following code snippet shows how to check for the existence of the IBX component Security Version on a client computer from the Rights Manager Server. (Verify that that the client system reports Security Version of 2.8 or greater.)

Get the secure DRM component (individualization) version.
Set LicenseObj = Server.CreateObject("wmrmobjs.wmrmlicgen")
LicenseObj.ClientInfo = strClientInfo
LicenseObj.GetClientVersion cat2, ver2
iSecurityVersion_major = round(ver2/256)
iSecurityVersion_minor = ver2 mod 256

If the user's machine is on a platform that supports the update, you can initiate a re-individualization in one of two ways:

1) Send them to this web site, which will force a re-indiv (requires Internet Explorer).

http://drmlicense.one.microsoft.com/Indivsite/en/indivit.asp

2.) Use the FSDK APIs referenced below, which will force a re-indiv (requires an FSDK Certificate).

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmform95/htm/individualizingdrmapplications.asp

If you have any questions, comments, or concerns, please contact [email removed]. Thank you for your continued understanding and confidentiality as we resolve these critical matters.

Best Regards,
Joseph R. Jones
Breach Response Program Manager
Consumer Media Technologies
Microsoft Corp.
------------------------------

[valiant2]

Microsoft requires the content service providers to push the individualisations out to thier customers ...

This looks like a statement they made a couple of weeks ago. As far as I'm aware they've issued no updates and made no response to the latest version (1.3) of FairUseWM; so MS DRM remains compromised. Can someone correct me if I'm wrong? In any case everything has gone really quiet on the subject. I bet Microsoft have finally learnt their lesson and have gone back to the drawing board.

As I've posted to the main thread, the only recent development of any consequence is that (as of today) a UK based content provider (Sky Broadband) seems to have re-instated their DRM based content service, having withdrawn it a few weeks ago. Whether this means that Microsoft have issued an update that nobody has heard of (unlikely) or Sky have decided that they can't wait any longer (most likely) remains to be seen.