Hi Christian,
Le 24/08/2016 à 12:58, Christian Lohmaier a écrit :
Hi Jean-Baptiste, *,
On Wed, Aug 24, 2016 at 12:49 PM, Christian Lohmaier
<lohmaier@googlemail.com> wrote:
On Wed, Aug 24, 2016 at 12:24 PM, Jean-Baptiste Faure
<jbfaure@libreoffice.org> wrote:
Hi,
According to this article :
https://www.infoq.com/news/2016/06/visual-cpp-telemetry
I am wondering if MS-Windows builds of LibreOffice are affected.
Without looking in detail, the article ends with:
"VS2012 and VS2013 do not include this telemetry behavior."
As builds are done with VS2013 currently, the answer is "No, TDF
provided builds are not affected".
Thank you for your answer. Now I can answer if an end-user asks the
question. :-)
And looking at the acutal reddit thread/source for that article, I see
the post by Steve Carrol:
https://www.reddit.com/r/cpp/comments/4ibauu/visual_studio_adding_telemetry_function_calls_to/d30dmvu
→ update 3 to VS 2015 alraedy is available, so even when using 2015
shouldn't be a problem.
So more or less outdated post, wonder where you did stumble upon that
post now - even the responses by Steve Carrol (from which only one is
referred to in the atrticle) is three months old...
In a thread about W10 privacy problems in a French mailing-list.
Best regards.
JBF
--
Seuls des formats ouverts peuvent assurer la pérennité de vos documents.
Disclaimer: my Internet Provider being located in France, each of our
exchanges over Internet will be scanned by French spying services.
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.