Its a little unclear from the article, but are they saying that the "maliciously encoded macros and templates" are M$ formatted files or ODF formatted files (using OOo owns macro language)... And what does "compromise systems running the open-source software" - are we talking taking over admin privileges, crashing the system, remote exploits, what?? (can't read French so can't get answers from linked presentation either).
I still think, as I did last time there was a security "scare" with OOo, that if you open documents from unknown sources and let all the macro's run unhindered then you deserve what you get... Bit of a non-event in my book. /paul On 8/15/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Chad wrote: > Thought you might want to check this out. I don't remember seeing this on > any of the lists. The initial announcement was a couple of weeks ago. The most recent gives a list of "security flaws" in OOo on _Windows_. People who practice "safe computing" don't have anything to worry about. People who happily let all and sundry run on their machine will have a security problem. xan jonathon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
