4 ms·
The Go module hash checking seems to be more about avoiding the problems encountered by other language repos integrity and versioning issues (cough NPM), and in
by zdw 7y ago
The Go module hash checking seems to be more about avoiding the problems encountered by other language repos integrity and versioning issues (cough NPM), and in terms of tracking it seems about as invasive as Debian's popcon.
Enabled by default can and should be the default for security-related features.
I tend to agree about the rest of the creepiness, especially anything personally behavioral.
- ptx 7y agoDebian's popcon is not enabled by default.
- dsr_ 7y agoDebian's popcon is really irritating because Debian actually uses it as a source of evidence... systematically eliminating those of us who keep it off for privacy/security reasons.
- calcifer 7y agoLet me get this straight. You have an opt-in way of telling them what you use, which you don't use and then get upset because your use isn't considered? What should do they do, send a surveyor to your house? Sound decision making requires metrics. If you opt-out of metrics, you don't get to participate in decisions.
- TeMPOraL 7y ago> What should do they do, send a surveyor to your house? Not use data from a mechanism that's controversial with some of the user base to drive decisions? Reach out and ask people, instead of asking their machines? > Sound decision making requires metrics. If you opt-out of metrics, you don't get to participate in decisions. Sound decision making requires some kind of metrics and also sound reasoning. It doesn't mean that metrics have to be widely-deployed telemetry. There are alternatives, like doing studies "the old way". Moreover, it can be argued that a lot of problems on today's Internet stem from people vacuuming up whatever data they can find and divining decisions out of it. It's not how you do science.
- ChoGGi 7y ago> Not use data from a mechanism that's controversial with some of the user base to drive decisions? Reach out and ask people, instead of asking their machines? That would require more time and money that could be spent elsewhere.
- TeMPOraL 7y ago"It's cheaper this way" is not a valid justification for doing the wrong thing over the right thing.
- zajio1am 7y ago> Reach out and ask people, instead of asking their machines? So you would have statistics biased by not accounting for people not bothered to answering these questions instead of not accounting for people not using popcon?
- TeMPOraL 7y agoYou'd have statistics biased towards people caring to express their opinions. You also wouldn't mistakenly assume that because something isn't regularly used it's also not needed.
- jodrellblank 7y ago> If you opt-out of metrics, you don't get to participate in decisions. Would you agree to a Democracy where the government put sensors in your house, then told you which candidate your vote would be counted towards from your behaviour? And if you opted out of that, you don't get to participate at all?
- dsr_ 7y agoSound decision making requires reasonable metrics. To quote the lead dev of popcon when someone said that they couldn't recommend it due to specific concerns: "If you deal with people with strict security/privacy requirement, you are correct to do so. I would do the same."
- phjesusthatguy3 7y agoIt isn't, but it's installed by default, and I'm always amused when I get to that installation step. "Do you want to tell us about your system?" answer no "installing popularity-contest"
- SomeOldThrow 7y ago> in terms of tracking it seems about as invasive as Debian's popcon. How do you figure?
- raxxorrax 7y ago> Enabled by default can and should be the default for security-related features. Not since Google uses the argument of increased security to justify data collection for quite some time in the interest of itself.
- jhall1468 7y agoYou are free to setup your own DB if that's a concern for you. It's a totally justified concern, but this is just concern-trolling. Most people would use this either way. People with strong privacy concerns may setup their own DB, but they represent the minority (despite the heavily privacy-biased stance of HN users). If you're in the minority, you should expect to have to do more work to get the right balance of security and privacy.
- raxxorrax 7y agoI am just criticizing collecting data under the veneer of security or creating a dependence at this point. These are two completely separate issues and the argument for security is used to justify questionable practices. > If you're in the minority, you should expect to have to do more work to get the right balance of security and privacy. It is exactly this false dichotomy that I am criticizing here, because it is completely baseless. You are reading an article that hints to privacy violations. You can only be secure if your privacy is protected. That is the causal relation between these two needs.
- jhall1468 7y ago> I am just criticizing collecting data under the veneer of security or creating a dependence at this point. This isn't a veneer. It's a signature check to ensure a package is what it says it is. Have you seen the hassle npm routinely goes through because of this? A centralized, trusted server is a sensible "default" setting. The fact that they offer a self-hosted solution is a great benefit. > You can only be secure if your privacy is protected. That is the causal relation between these two needs. Nonsense. I can have a completely secure system and everyone knows who I am. I can have an entire insecure system with zero means of identifying the owner and thus, remain private. You aren't just conflating privacy and security, you are implying a casual relationship between them. Both are nonsense.
- nindalf 7y agoOn HN it is taken as gospel that any information sent to a server will absolutely compromise your privacy. If anyone points out that the information is trivial or useless the rebuttal is instant - it can be cross referenced with other sources to build a complete profile of you. If you want to know which Go modules I use, go check out my github. They're listed right there in import statements. If I'm hacking on a project that I want to keep private, I'll disable this feature with a command line flag - easy. My issue with the paranoid folks in that thread is not that they made no sense (they can't help that), it was they were attacking the person who implemented the feature viciously. He had implemented a feature that a majority of Go developers had been requesting for 5+ years, had done it in a way that improved clean build time, improved security and could easily be disabled or replaced with a private DB. Literally what else could that man have done? Even though all his work could be verified trivially (Go is open source!), they still chose to attack him.
- deleted 7y ago[deleted]
- stonogo 7y ago> Literally what else could that man have done? He could have not sent all build-time network accesses to Google by default. It's that simple.
- nindalf 7y agoNo it isn't. Please tell me how you achieve security without storing hashes in a DB? The default is only for those who'd prefer not to run their own DB. You are welcome to run your own DB if you want. Why are you so upset that other people will be using a feature you obviously won't? Why are you upset when this leaks literally no info that your github repo doesn't already?
- ori_b 7y ago> No it isn't. Please tell me how you achieve security without storing hashes in a DB? I bet the DB is small enough that you could default to just downloading it and syncing on your machine.
- kerng 7y agoGoogle (as well as surveillance states) use security arguments conveniently a bit too often to try and justify their actions.