Please do NOT send to me directly, I'm on the list.
On 4/17/2014 4:13 PM, Cley Faye <cleyfaye@gmail.com> wrote:
2014-04-17 21:52 GMT+02:00 Tanstaafl <tanstaafl@libertytrek.org>:
This is an OpenSSL bug, what does this have to do with Libreoffice?
As far as I can tell, it's because LibreOffice was linked with a
"vulnerable" version of openssl.
Again... in what way was Libreoffice 'linked' to OpenSSL???????
Libreoffice is NOT a communication package utilizing TCP/UDP
connections, so, in what possible way could the heartbleed bug affect
Libreoffice?
It's never bad to be on the side of precautions by using the latest
versions (especially if it provides bugfixes), but I'm not sure how an
exploit on the server side of a TLS connection could cause issue in a
client software. Better safe than sorry I suppose.
Are you talking about the libreoffice WEBSITE? Thatr is completely
different and totally unrelated to the SOFTWARE ON the site...
Of course, unless you are concerned that the available downloads were
replaced with infected versions... which I guess is not impossible.
--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.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.libreoffice.org/global/users/
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.