<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Office 2003 bug locks you out of your documents</title>
	<atom:link href="http://www.askwoody.com/2009/office-2003-bug-locks-documents/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.askwoody.com/2009/office-2003-bug-locks-documents/</link>
	<description>Woody Leonhard’s no-bull news, tips and help for Windows and Office</description>
	<lastBuildDate>Wed, 08 Feb 2012 17:06:02 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Herby Sagues</title>
		<link>http://www.askwoody.com/2009/office-2003-bug-locks-documents/comment-page-1/#comment-2394</link>
		<dc:creator>Herby Sagues</dc:creator>
		<pubDate>Fri, 02 Apr 2010 23:06:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.askwoody.com/?p=3366#comment-2394</guid>
		<description>The message said that you &quot;should try again later&quot;. And trying again later (24 hours later, when the fix was issued) actually solved the problem. So I would say the message was quite accurate :-)

Now, regarding your aversion to DRM, I can understand that when talking about media and other stuff you expect to &quot;own&quot;. Also, about anything that&#039;s of mass appeal, since the &quot;break once, use anywhere&quot; mantra applies. 
But for corporate documents I don&#039;t see what&#039;s the problem. 
If you&#039;ve ever worked at a large company you&#039;ll know that users can&#039;t always be trusted to keep confidential information that&#039;s available to them confidential. No, it is not a matter of training (though training helps) as the continous leakages we see indicate. If it is a matter of just clicking the &quot;forward&quot; button or saving a document into a pen drive, and users can claim they didn&#039;t know it was wrong, they&#039;ll do it.
Yes, this type of DRM (whcih Microsoft calls IRM to differentiate it from the media stuff) is not hacker-proof, and it is not supposed to be. It is supposed to help enforce information policies at a company. 

And it does work. I&#039;ve been following data leakage incidents for long, and I&#039;m yet to see a single one where documents protected with this type of solution from any vendor have actually been disclosed in any other way than &quot;rumors&quot;. Yes, it is technically possible that it might happen, but in practice it doesn&#039;t since users are very reluctant to break the rules when they cannot later claim it was an accident, or that they didn&#039;t know it was wrong.
So you have a solution that effectively works, that has minimal risk (your documents could get locked by a flaw in the system, just like with any encryption solution unless you know the keys by memory), is easy to use and compatible with most documents users create and you consider that &quot;a piece of &amp;#%*!&quot;? 
I don&#039;t get it.</description>
		<content:encoded><![CDATA[<p>The message said that you &#8220;should try again later&#8221;. And trying again later (24 hours later, when the fix was issued) actually solved the problem. So I would say the message was quite accurate <img src='http://www.askwoody.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Now, regarding your aversion to DRM, I can understand that when talking about media and other stuff you expect to &#8220;own&#8221;. Also, about anything that&#8217;s of mass appeal, since the &#8220;break once, use anywhere&#8221; mantra applies.<br />
But for corporate documents I don&#8217;t see what&#8217;s the problem.<br />
If you&#8217;ve ever worked at a large company you&#8217;ll know that users can&#8217;t always be trusted to keep confidential information that&#8217;s available to them confidential. No, it is not a matter of training (though training helps) as the continous leakages we see indicate. If it is a matter of just clicking the &#8220;forward&#8221; button or saving a document into a pen drive, and users can claim they didn&#8217;t know it was wrong, they&#8217;ll do it.<br />
Yes, this type of DRM (whcih Microsoft calls IRM to differentiate it from the media stuff) is not hacker-proof, and it is not supposed to be. It is supposed to help enforce information policies at a company. </p>
<p>And it does work. I&#8217;ve been following data leakage incidents for long, and I&#8217;m yet to see a single one where documents protected with this type of solution from any vendor have actually been disclosed in any other way than &#8220;rumors&#8221;. Yes, it is technically possible that it might happen, but in practice it doesn&#8217;t since users are very reluctant to break the rules when they cannot later claim it was an accident, or that they didn&#8217;t know it was wrong.<br />
So you have a solution that effectively works, that has minimal risk (your documents could get locked by a flaw in the system, just like with any encryption solution unless you know the keys by memory), is easy to use and compatible with most documents users create and you consider that &#8220;a piece of &amp;#%*!&#8221;?<br />
I don&#8217;t get it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

