More coal on the fire

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: Fred Wright
Date:  
Subject: More coal on the fire
--=====================_575448==_.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed

The following is From the Lockergnome Tech Specialist Newsletter. This is
another action on MS's part that might give folks impetus to move at least
to OpenOffice - -

Word Security Flaw Poses Threat - MS Responds

<http://www.microsoft.com/technet/security/topics/secword.asp>http://www.microsoft.com/technet/security/topics/secword.asp


A new Microsoft Word flaw has surfaced that could result in documents being
exposed to prying eyeballs. I think Microsoft did a good job with
explaining the basics of how the bug works and how best to protect against
its effects. It's clear from the text, however, that Office 97 users, which
comprise a significant 30% of the Office user base, will be left out in the
cold when it comes to a fix. They note that Office 97 was created in
another era (as if it's been decades since the release) and security
architecture has been improved greatly since then. Call me silly, but
offering up a helpful nudge into Office XP as a "fix" for a bug that works
the same way in all affected versions seems rather patronizing to the 30%
of their patronage.



Fred Wright

--=====================_575448==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<font face="Courier New, Courier">The following is From the Lockergnome
Tech Specialist Newsletter.&nbsp; This is another action on MS's part
that might give folks impetus to move at least to OpenOffice -
-<br><br>
</font><font face="Courier New, Courier" size=2>Word Security Flaw Poses
Threat - MS Responds <br><br>
<a href="http://www.microsoft.com/technet/security/topics/secword.asp">http://www.microsoft.com/technet/security/topics/secword.asp</a>
<br><br>
A new Microsoft Word flaw has surfaced that could result in documents being exposed to prying eyeballs. I think Microsoft did a good job with explaining the basics of how the bug works and how best to protect against its effects. It's clear from the text, however, that Office 97 users, which comprise a significant 30% of the Office user base, will be left out in the cold when it comes to a fix. They note that Office 97 was created in another era (as if it's been decades since the release) and security architecture has been improved greatly since then. Call me silly, but offering up a helpful nudge into Office XP as a &quot;fix&quot; for a bug that works the same way in all affected versions seems rather patronizing to the 30% of their patronage. <br><br>
<br>
</font><x-sigsep><p></x-sigsep>
Fred Wright<br>
</html>

--=====================_575448==_.ALT--