Getting data about which commands are used most, if they're successful or throwing errors, possible typos, unclear command flags, etc, are useful when shipping software frameworks used by 10s of millions to build products that run the entire Fortune 500 and thousands of other businesses.
This is not ubiquitous spyware, and is about as generic as it gets while still remaining useful. Every software company (many of which are featured here on HN) does the same analytical tracking to figure out how their products are being used and it results in better features. What exactly is the danger here, especially with the lack of personal info and an opt-out method?
They even make the data public along with insights into how it helped: https://blogs.msdn.microsoft.com/dotnet/2017/07/21/what-weve...
Imagine I ran a command "make.exe my-secret-project-name" or "make.exe process_gdrp_removal_request SOME_SSN".
And as the linked page admits, they really do collect all command line arguments, not just a white list of valid commands. Perhaps someone accidentally pastes an AWS API Secret into the wrong terminal window and it ended up as "dotnet.exe MY_AWS_SECRET". ("You will notice misspellings, like “bulid”. That’s what the user typed. It’s information").
Pushing a secret API key to github, even accidentally, does not happen covertly or as an unexpected side effect of some other tool written by github, and you'll soon realize what happens because you'll see your key sitting there. You also have a general idea of what you are playing with when you start using github, whether it's private repos or public repos.
Having a local CLI tool submit your secret API key as part of telemetry collecting command line arguments is totally unexpected and invisible for the user, and you won't even see it has happened.
https://github.com/dotnet/cli/pull/2145
"My understanding is that this was recently discussed with our privacy team and we concluded that collecting the arguments themselves (hashed or not) is not acceptable per our privacy policies. Not sure whether the code already reflects that, but it's being worked on."
Somebody in the thread for the issue said it's "not acceptable per our privacy policies" and "being worked on" two years ago, but did they ever actually stop collecting command line arguments?
While I'm not defending the practice, I don't see how, when you make a copy-paste mistake into a wrong app, you blame the app for receiving the result of that mistake?
Yes. People all make mistakes. Good tools mitigate mistakes, while bad tools (like this telemetry) exacerbates problems.
Is the difference not obvious?
When you run make.exe some-program-that-uses-aws YOUR_AWS_SECRET intentionally it is troublesome by itself.
You have a strange notion that small troubles and big troubles are all the same.
Does it happen in other apps? Sure. But I would not expect my command-line builds are phoning home what exactly I am doing.
https://github.com/dotnet/cli/blob/b45f1fb439b36872c249b07f1...
Exactly. Command line tools don't usually collect your data and send it off somewhere without asking. You wouldn't expect ls, cat and grep to spy on you. That's why it's so surprising.
But even big interactive applications like IDEs don't normally do this without asking. IntelliJ had a dialog pop up just a few days ago to ask me nicely to participate, defaulting to non-participation (!). Visual Studio and Office used to do the same thing, as I recall.
(Additionally, once you figure out how to opt-out in .NET Core, does it tell you somehow that you did so successfully? I think I've set the environment variable correctly, but how can I be sure?)
Except in Ubuntu Linux where apt-get it has done so for ages without anyone complaining:
https://askubuntu.com/questions/57808/what-is-the-popularity...
I think it comes from Debian[1] actually, where it's also opt-in – my Debian machine doesn't have it installed. Like it says in the Debian package description: "Vote for your favourite packages automatically". It's voting, not spying – strictly voluntary. Those of us who don't want to vote don't have to.
Fair enough, but it wasn’t always like that.
> “Vote for your favourite packages automatically". It's voting, not spying
That’s just playing with words. What it does is exactly the same: provide the upstream author statistics about what is being used and not.
Surely you can’t mean that this is a serious argument.
When people go to vote for their government, is that implemented by sending government agents to eavesdrop on people's conversations to suss out what their political preference might be? No. People voluntarily (this is the core of my analogy) go to vote, to make their voice heard.
That's the difference between voting and spying.
Of course, if popcon were enabled by default, then that would be different and not like voting at all! But that's not what it said on the page you linked.
OpenJDK is fine however.
The installers I've been getting directly from the Oracle JDK pages haven't installed anything extra, or asked to.
It's of course possible that some users don't experience these "sponsored offers" due to geotargeting, A/B-testing, lack of available "offers" at a specific time, or any other reason controlled by the server side of the installer.
And also for what it's worth, it appears that they are using this ID to correlate what users are doing across their products - as indicated by this comment: "// The hashed mac address needs to be the same hashed value as produced by the other distinct sources given the same input. (e.g. VsCode)" (https://github.com/dotnet/cli/blob/b45f1fb439b36872c249b07f1...)
Edit looks like it can be disabled with the "DOTNET_CLI_TELEMETRY_OPTOUT" environmental variable, following https://github.com/dotnet/cli/issues/3093#issuecomment-22997...
A little while back, an update to Office for Mac caused each application to pop a dialog on startup to share "diagnostic data" with Microsoft. The only options were "Full" and "Basic" data sharing. The buttons in the dialog were "Accept" (once you'd clicked an option) and "Learn More". No "Don't Share Data" option.
Many users complained in the support forums about this, saying they wanted a way to completely opt out. Worse: if you closed the dialog without selecting any option, you were automatically "opted in" to "Full" data sharing (as you could see if you then went into settings and looked at the privacy tab).
This week they rolled out another update. Which sneakily looks like it fixed this; now the dialog has buttons "No" and "Yes", but if you read it the question it's asking is "Can Office send enhanced error reporting?" There still is not a "do not share data" option.