4 ms·

How safe, audited and non-invasive is .net core by now? There's a .net program I have a VM for and that's kind of a pain. Since .net had telemetry by default, r

by lvass 5y ago

How safe, audited and non-invasive is .net core by now? There's a .net program I have a VM for and that's kind of a pain. Since .net had telemetry by default, running bare on my machines was never an option, and Mono wouldn't even work.

tester756 5y ago
>Since .net had telemetry by default, running bare on my machines was never an option Why? I don't see anything weird in data collected https://docs.microsoft.com/en-us/dotnet/core/tools/telemetry#data-points https://docs.microsoft.com/en-us/dotnet/core/tools/telemetry...
- AlexanderDhoore 5y ago
  Medical, military, industrial... Not everything is a webapp.
  - tester756 5y ago
    OP wrote about his private machine. Anyway, OP was worried about installing .NET because it has telemetry by default, meanwhile you can disable telemetry before running your war-app or just ship standalone? idk.
    - lvass 5y ago
      I never said what "my machines" do. Don't assume everyone has the same lax safety necessities as you have.
      - tester756 5y ago
        Fair, that's why I asked which specific telemetry is weird/insecure in your opinion
      - nojito 5y ago
        It's downright impossible find a situation where .NET is not approved for use because of "security".
brushfoot 5y ago
.NET doesn't have telemetry. The .NET SDK does by default, but that's for developing, not running, .NET apps. You don't need to (and shouldn't) install the SDK on a production machine. In other words, if you just downloaded the .NET or .NET Core runtime to host an app, there's no .NET telemetry. As far as the .NET SDK, you can disable telemetry by setting the environment variable `DOTNET_CLI_TELEMETRY_OPTOUT` to `1` or `true`.
tasogare 5y ago
In which kind of world do you live that setting a single environment variable is too much technical work?[0] I have the feeling your post is more about shitting on .NET with a low effort excuse than genuine interest. [0] set DOTNET_CLI_TELEMETRY_OPTOUT environment variable to 1 or true

by lvass 5y ago

tester756 5y ago

>Since .net had telemetry by default, running bare on my machines was never an option Why? I don't see anything weird in data collected https://docs.microsoft.com/en-us/dotnet/core/tools/telemetry#data-points https://docs.microsoft.com/en-us/dotnet/core/tools/telemetry...

AlexanderDhoore 5y ago
Medical, military, industrial... Not everything is a webapp.
- tester756 5y ago
  OP wrote about his private machine. Anyway, OP was worried about installing .NET because it has telemetry by default, meanwhile you can disable telemetry before running your war-app or just ship standalone? idk.
  - lvass 5y ago
    I never said what "my machines" do. Don't assume everyone has the same lax safety necessities as you have.
    - tester756 5y ago
      Fair, that's why I asked which specific telemetry is weird/insecure in your opinion
    - nojito 5y ago
      It's downright impossible find a situation where .NET is not approved for use because of "security".

brushfoot 5y ago

.NET doesn't have telemetry. The .NET SDK does by default, but that's for developing, not running, .NET apps. You don't need to (and shouldn't) install the SDK on a production machine. In other words, if you just downloaded the .NET or .NET Core runtime to host an app, there's no .NET telemetry. As far as the .NET SDK, you can disable telemetry by setting the environment variable `DOTNET_CLI_TELEMETRY_OPTOUT` to `1` or `true`.

tasogare 5y ago

In which kind of world do you live that setting a single environment variable is too much technical work?[0] I have the feeling your post is more about shitting on .NET with a low effort excuse than genuine interest. [0] set DOTNET_CLI_TELEMETRY_OPTOUT environment variable to 1 or true