Hi NoOp,
On Fri, Mar 23, 2012 at 2:56 AM, NoOp <glgxg@sbcglobal.net> wrote:
On 03/22/2012 06:31 PM, Italo Vignoli wrote:
NoOp wrote:
It would be nice if someone 'official' (ala TDF) could post the
CVE-2012-0037 notice on both the user and announce lists.
The public was not supposed to know of this CVE, people should be
given time to update to the fixed version before.
See e.g.
http://blog.documentfoundation.org/2011/10/05/the-document-foundation-publishes-details-of-libreoffice-3-4-3-security-fixes/
"Following industry best practice, details of security fixes are
withheld until users have been given time to migrate to the new
version."
But Apache-OOo made it public on their list, so we also had to make
the info available.
http://mail-archives.apache.org/mod_mbox/incubator-ooo-dev/201203.mbox/%3CCAP-ksoj7o5%2B2YH-E4XzR044V0e3YZfZvuef7eJuNGhdy%2Bk9kyA%40mail.gmail.com%3E
Neither do the release logs or release notes.
As above - this was intentional. No details about the security fixes
until the upstream project makes the CVE public (the bug is in a
third-party component that is shipped along with LibreOffice).
That of course doesn't mean it shouldn't be added now that the CVE is public.
ciao
Christian
--
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted
Context
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.