4 ms·
> Perhaps someone accidentally pastes an AWS API Secret into the wrong terminal window and it ended up as "dotnet.exe MY_AWS_SECRET". While I'm not defending t
by smhg 8y ago
> Perhaps someone accidentally pastes an AWS API Secret into the wrong terminal window and it ended up as "dotnet.exe MY_AWS_SECRET".
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?
- 0x0 8y agoAny tool that purposefully builds in unnecessary minefields like these deserves to be shamed.
- netheril96 8y ago> 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.
- smhg 8y agoSo when you paste your secrets by mistake into your browsers' instant-search box, you blame your browser for sending that data over the network?
- 0x0 8y agoOf course not. The browser performed its primary task, and the consequences are reasonably obvious to the user, who can at least make an informed corrective action. Is the difference not obvious?
- smhg 8y agoI think I should have said: the accidental paste is irrelevant here. It will always be troublesome if you paste secrets in the wrong place (especially if it takes it to the network). When you run make.exe some-program-that-uses-aws YOUR_AWS_SECRET intentionally it is troublesome by itself.
- netheril96 8y ago> It will always be troublesome You have a strange notion that small troubles and big troubles are all the same.
- slenk 8y agoI would say there is a different expectation of privacy. When I am executing arguments on my command line, I am not expecting it to get collected and sent anywhere. Does it happen in other apps? Sure. But I would not expect my command-line builds are phoning home what exactly I am doing.