Member Sign In
Not a member?

A Wired.com user account lets you create, edit and comment on Webmonkey articles. You will also be able to contribute to the Wired How-To Wiki and comment on news stories at Wired.com.


It's fast and free.

Sign in with OpenID
Sign In
Webmonkey is a property of Wired Digital.
processing...
Join Webmonkey

Please send me occasional e-mail updates about new features and special offers from Wired/Webmonkey.
Yes No

Please send occasional e-mail offers from Wired/Webmonkey affiliated web sites and publications, and carefully selected companies.
Yes No

I understand and agree that registration on or use of this site constitutes agreement to Webmonkey's User Agreement and Privacy Policy.
Webmonkey is a property of Wired Digital.
processing...

Retrieve Sign In

Please enter your e-mail address or username below. Your username and password will be sent to the e-mail address you provided us.

or
Webmonkey is a property of Wired Digital.
processing...

Welcome to Webmonkey

A private profile page has been created for you.
As a member of Webmonkey, you can now:
  • edit articles
  • add to the code library
  • design and write a tutorial
  • comment on any Webmonkey article
Close
Webmonkey is a property of Wired Digital.

Sign In Information Sent

An e-mail has been sent to the e-mail address registered in this account.
If you cannot find it in your in-box, please check your bulk or junk folders.
Sign In
Webmonkey is a property of Wired Digital.

Microsoft Apologizes for Disabling File Formats in Office Update

msoffice.jpgLast week we mentioned that the SP3 update for Microsoft Office blocked users from opening older file formats which Microsoft had deemed “insecure.” Members of the Microsoft Office team have since issued apologies for erroneously blaming the software’s own shortcomings on the file formats themselves and has posted some new tools to let users of Office 2003 SP3 unblock a number of file types.

David LeBlanc, a senior software development engineer with the Microsoft Office team, writes in a post on his blog that Microsoft made a mistake in attributing security problems to certain file formats.

“We stated that it was the file formats that were insecure,” writes LeBlanc, “but this is actually not correct.” Which is what we also said when news of the blocked files first surfaced. As LeBlanc correctly says, “a file format isn’t insecure — it’s the code that reads the format that’s more or less secure.”

LeBlanc goes on to note that the code in Office that handles older file formats isn’t “as robust as the code we’ve written more recently, which is part of our decision to disable them by default.”

LeBlanc also apologizes for implying that there were any insecurities in the file formats of some of its competitors like Corel, whose .cdr files were initially blocked by the update.

LeBlanc also swallows some pride to admit that “we also recognize that we have not made any of this as usable as we’d like, and we apologize that this hasn’t been as well documented or as easy as you need it to be.”

In other words Microsoft has accepted the blame and offered a solution, which we applaud. With the whole debacle coming at a time when Office competitors like online suites and OpenOffice continue to gain ground, the mea culpa may be a nice gesture, but we can’t help wondering how much it will mediate the damage and broken trust among users.

[via ComputerWorld]

See Also:

Post Comment Comments Permalink Print
Reddit Digg

 
Subscribe now

Special Offer For Webmonkey Users

WIRED magazine:
The first word on how technology is changing our world.

Subscribe for just $10 a year