Author Topic: Microsoft repackages apps with a telemetry .NET wrapper  (Read 211 times)

0 Members and 2 Guests are viewing this topic.

Offline madiresTopic starter

  • Super Contributor
  • ***
  • Posts: 7764
  • Country: de
  • A qualified hobbyist ;)
Microsoft repackages apps with a telemetry .NET wrapper
« on: April 21, 2024, 08:13:53 am »
https://twitter.com/WithinRafael/status/1781743054296432772:

Quote
The Microsoft Store team has started quietly wrapping apps, like EarTrumpet, with some malware-looking .NET executable wrapper (with my app's name of course) chock full of telemetry and other code. They also target netfx 4.7.2 when my app targets netfx 4.6.2, wtf?
 

Online RoGeorge

  • Super Contributor
  • ***
  • Posts: 6202
  • Country: ro
Re: Microsoft repackages apps with a telemetry .NET wrapper
« Reply #1 on: April 21, 2024, 02:52:56 pm »
Similar they do with the VScode, the rumor is.  They only add the telemetry in the binaries.

Quote
    When we [Microsoft] build Visual Studio Code, we do exactly this. We clone the vscode repository, we lay down a customized product.json that has Microsoft specific functionality (telemetry, gallery, logo, etc.), and then produce a build that we release under our license.

    When you clone and build from the vscode repo, none of these endpoints are configured in the default product.json. Therefore, you generate a “clean” build, without the Microsoft customizations, which is by default licensed under the MIT license
Source:  https://vscodium.com/#why-does-this-exist

Offline SiliconWizard

  • Super Contributor
  • ***
  • Posts: 14466
  • Country: fr
Re: Microsoft repackages apps with a telemetry .NET wrapper
« Reply #2 on: April 21, 2024, 08:26:59 pm »
Nice. :-+
 

Offline Perkele

  • Contributor
  • Posts: 49
  • Country: ie
Re: Microsoft repackages apps with a telemetry .NET wrapper
« Reply #3 on: April 21, 2024, 08:59:32 pm »
Similar they do with the VScode, the rumor is.  They only add the telemetry in the binaries.

Quote
    When we [Microsoft] build Visual Studio Code, we do exactly this. We clone the vscode repository, we lay down a customized product.json that has Microsoft specific functionality (telemetry, gallery, logo, etc.), and then produce a build that we release under our license.

    When you clone and build from the vscode repo, none of these endpoints are configured in the default product.json. Therefore, you generate a “clean” build, without the Microsoft customizations, which is by default licensed under the MIT license
Source:  https://vscodium.com/#why-does-this-exist

Just a heads-up warning - add-ons in VSCodium can't be installed from directly Store, you need to download and install them manually.
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf