Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index

On Fri, 2012-03-23 at 08:10 -0400, drew jensen wrote:
On Fri, 2012-03-23 at 07:55 -0400, Dan Lewis wrote:
Using both LO and OOo, I'm aware of the need to patch this
vulnerability for both. What I don't know is what is the status of this
with respect to LO. I presently have 3.5.1-102 and I did not
see anything mentioned about this on the LO main page. It would be nice
to have a statement on the home page when it was fixed for 3.4.x and
3.5.x. It would be nice to have something on this mailing list.

Hi Dan

3.4.6 for the patch. It was in the release announcement. 

Not sure but it maybe that 3.5.1 also has the fix - 3.5.2 surely will.


     I have now read the release announcement, and it contains
announcements for both 3.4.6 and 3.5.1. Both of these are rather vague.
     The 3.4.6 announcement mentions fixing a potential security issue.
The 3.5.1 states: "LibreOffice contains all the security fixes from in 3.3.0, and perhaps more as a side-effect of the code
     What security issues? I'm not sure I know from what I read.
     Another thing that comes from trying to find this information: What
is a link that I can use to list my concerns or other comments about the
layout of the LO website?


For unsubscribe instructions e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.