While the Microsoft announcement of the problem
(http://www.microsoft.com/technet/security/advisory/912840.mspx) is a
masterpiece of content-free verbiage putting the best face on a bad situation,
Microsfot has not yet provided a fix. The Registry setting fixes do provide
workaround protection, albeit at some loss of function. (The safety is probably
worth it.)

A fix patch has been developed and provided by Ilfak
Guilfanov. He is one of the lead programmers on the IDA Pro disassembler
product. Details of both the exploit and the fix can be found at
http://www.hexblog.com/2005/12/wmf_vuln.html. The patch itself can also be
obtained from that site, as well as others that are mirroring it in case of
overload.
The patch seems to be undergoing fairly rapid development: the first mention I
saw was of wmffix_hexblog11.exe, but when I got to the page it was showing
wmffix_hexblog13.exe.
(http://www.hexblog.com/security/files/wmffix_hexblog13.exe, if you want to try
it direct.)

The author notes the possibility of a potential loss of functionality with the
patch. I have not seen reports of testing at this point: most will probably
want to
wait for some usage reports before rolling out this patch.

====================== (quote inserted randomly by Pegasus Mailer)
rslade@... slade@... rslade@...
On the side of the software box, in the System Requirements part,
it said Requires Windows 95 or better. So I installed Linux
http://victoria.tc.ca/techrev or http://sun.soci.niu.edu/~rslade