Re: [Libreoffice] LibO security

2011-02-08 Thread Thorsten Behrens
Michael Meeks wrote: > We could do worse than cutting / pasting / editing point two of: > http://people.gnome.org/~michael/blog/2011-02-04.html into the release > notes (or something). > Added a short notice, and a link to that blog post. Let's work on a more formal approach to this for the

Re: [Libreoffice] LibO security

2011-02-08 Thread Michael Meeks
On Tue, 2011-02-08 at 08:22 +0100, Thorsten Behrens wrote: > yes, since we've merged all code from OOo 3.3.0 (with the exception > of one rather broken calc fix). .. > Well, we have. It's Cc-ed. What we prolly need is to properly > document this. We could do worse than cutting / pasting /

Re: [Libreoffice] LibO security

2011-02-08 Thread Kevin Hunter
At 2:22am -0500 Tue, 08 Feb 2011, Thorsten Behrens wrote: Well, we have. It's Cc-ed. What we prolly need is to properly document this. No no! They're just practicing good security: obscurity! ;-) Kevin ___ LibreOffice mailing list LibreOffice@lists

Re: [Libreoffice] LibO security

2011-02-07 Thread Thorsten Behrens
Nguyen Vu Hung wrote: > 1. My apologies if this has been posted >http://www.openoffice.org/security/bulletin.html >Did we get them fixed in 3.3.0? > Hi, yes, since we've merged all code from OOo 3.3.0 (with the exception of one rather broken calc fix). > 2. IMO, we need a security team,