PureBasic Forums - English

At first, yes I am one of the Windows spy update paranoics.

This website claims Visual Studio 2015 C++ Compiler secretly inserts Telemetry Code Into Binaries.

https://yro.slashdot.org/story/16/06/10 ... o-binaries

So I ask myself which Version was used to create the current PureBasic Version and how does it have effect at the programs we create with PureBasic?

slashdot.org wrote:... discovered recently that Visual Studio 2015 C++ compiler was inserting calls to a Microsoft telemetry function into binaries. "I compiled a simple program with only main(). When looking at the compiled binary in IDA, I see a call for telemetry_main_invoke_trigger and telemetry_main_return_trigger.

FWIW no files in the Purebasic 5.42 LTS package contain the word "telemetry" in any shape or form, my guess is i dont think it's an issue at all for PB or PB users, definitely something to keep an eye out for though when using VS2015 so many thanks for the alert! I'm trying to install VS2015 today but having problems registering, think i'll just stick with 2013 2010 and 2008 lol, only need it for building libs for PB anyway

kurzer wrote:At first, yes I am one of the Windows spy update paranoics.

This website claims Visual Studio 2015 C++ Compiler secretly inserts Telemetry Code Into Binaries.

https://yro.slashdot.org/story/16/06/10 ... o-binaries

So I ask myself which Version was used to create the current PureBasic Version and how does it have effect at the programs we create with PureBasic?

That website is fully right.
In past MS only inserted it's spy trash into PE header of executables (Rich Signature), now it come much far and modifies your code.
But It seems that 2010 and 2013 VC are clean of that.

The PB 5.40+ uses something from VC 2013 as I remember, and oldest versions were using 2010. Would be interesting to know details too, to be sure there are no any MS hit.

5th November 2012 : Version 5.00
- Updated: Use of VC++ 2010 instead of VC++ 2005 to compile the Windows libraries (32-bit and 64-bit), resulting of better optimized code

16th October 2015 : Version 5.40 LTS
- Updated: the Windows compiler to VC++ 2013 for better code generation

Lunasole wrote:In past MS only inserted it's spy trash into PE header of executables (Rich Signature)

very interesting!


so the dword after "Rich" is used as the key to decrypt the rest of it by simple XOR

Keya wrote: so the dword after "Rich" is used as the key to decrypt the rest of it by simple XOR

Not only, here is full review and code to decrypt it:
http://www.ntcore.com/files/richsign.htm

kurzer wrote:At first, yes I am one of the Windows spy update paranoics.

This website claims Visual Studio 2015 C++ Compiler secretly inserts Telemetry Code Into Binaries.

https://yro.slashdot.org/story/16/06/10 ... o-binaries

So I ask myself which Version was used to create the current PureBasic Version and how does it have effect at the programs we create with PureBasic?

Wasn't PB written in purely optimized ASM?!

- np

We use VC 2013

Fred wrote:We use VC 2013

@Fred,
is there a roadmap/plan about changing the Visual Studio version (maybe switch to VS2017 or VS2019)?

Thanks.