Paul wrote: > I would suggest that since this exploit seems to be a buffer overflow > within repair file routines it is due to dodgy M$ code within Excel.
That was my thought as well. If nothing else, and providing that OOo is _not_ affected, it's a good opportunity to move the last two Excel holdouts over to OOo. Perhaps someone on the OOo marketing/PR team could even get secunia.com to add this to their advisory: Solution: Open using OpenOffice > > Since OOo has its own way of repairing files, and its own code, I do > not think that OOo-calc would be effected. The true way would be of > course to test it... Yeah, I remember the "repairing" in 1.1 :-) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
