5 ms·
> can’t even scrape together $629 for something as essential as a software signature I don't think the $629 itself is the problem, but rather that they're bein
by TeMPOraL 3y ago
> can’t even scrape together $629 for something as essential as a software signature
I don't think the $629 itself is the problem, but rather that they're being forced to spend it on something that many people don't agree is "essential" in any way. Is it about security, or is it about crying "security" to push through a pay-to-play market?
- Derbasti 3y agoAnd moreso for a cross-platform tool. Essentially it's forcing devs to spend money on the Windows platform only, where they might prefer to spend it in a way that benefits all their users.
- keepamovin 3y agoIt’s a valid point you raise. Certainly conceivable. Whatever the security ramifications, however, the usability consequences are real and important. See my other comment for how i consider this may be cartel behavior: https://news.ycombinator.com/item?id=38056460 https://news.ycombinator.com/item?id=38056460
- TeMPOraL 3y agoMy point is slightly different. You're focusing on fees, and open source being an industry in itself. Quoting from the linked comment: > This lack of awareness hampers [open source community's] ability to participate effectively in the marketplace, including financial transactions to sustain itself. Thing is, a large part of that community doesn't want to "participate effectively in the marketplace". The community started as a way to refuse playing the market game. Good or bad, visionary or naive, this was the OG culture, and remains potent in a subset of the larger OSS world. > While I agree that small fees can serve as proof of identity—verifying that the software indeed comes from the claimed source, which seems to be one main intent of signatures—I don’t understand why these fees have to be exorbitant. Again, I don't think the price is the problem, nor even that there is a fee. The problem is that "verifying that the software indeed comes from the claimed source" is done by requiring the software to be developed or controlled by a specific legal entity, and requiring that entity to establish trust via business relationships with the network of companies centered around major software corporations. It's forcing the entire OSS ecosystem (or at least the parts that directly, or transitively, target proprietary platforms) to commercialize. Now, while I'm strongly biased against what I consider "security disempowering users and sucking out all the fun from computing", I'm not going to argue that this is entirely 100% bad, or that software devs have right to remain anonymous. Maybe, long-term, it's the only way forward. But right now, it feels like being colonized. "Yes, nice stuff you're making there, our citizens love it, and we've made some good money on it too. But from now on, you're no longer welcome on this land, unless you accept citizenship and become legible to our bureaucracy."
- keepamovin 3y agoThanks for your comprehensive response. I consider these topics deeply important, and worthy of a lot of consideration. I sensed we had a disagreement but likely tried to side step that to avoid any conflict, because I don’t really want to engage in that online. I’m glad to see I was right with my instinct and thank you for elaborating further just what any disagreement might be there! :) Please allow me some time to read, understand and consider what you said and maybe I’ll get back to you!
- TeMPOraL 3y agoThanks :). To be clear, I think what you wrote is true as well - it's a part of a larger picture. In my replies, I want to point at another part of that same picture, one I saw is not talked about at all in this thread, and which I believe may be more relevant to this case (because let's be honest, $629 for a project this widely used is peanuts, so it can't be the whole issue).
- keepamovin 3y agoBut maybe it is the issue. The guy is asking for money. He's not mounting a refusal of the whole system of signing. Everything in his announcement is about finding ways to accommodate himself to the new situation of having a certificate after a previous sponsor churned. His hesitation is clear, but a certificate there would cost $629 (tax excluded) for a single year, and his ask for sponsors is also very clear, and follows immediately: If your organization requires a signed installer then please consider sponsoring us with a code signing certificate. Please reach out to @dlemstra for questions or in case of a sponsorship. I understand the points you are making, but instead I think in this case it is not I who is missing the larger picture, but you--missing the larger picture, and one painted clearly in the text of the GitHub announcement this thread is about. However, in your other less relevant comment above, you raise interesting points which I want to address! While not as relevant to the specific case at hand, they are interesting and deep! Let's dive in over there! :)
- mike_hearn 3y agoYou can get certificates for individuals, not only companies.
- maccard 3y ago> but rather that they're being forced to spend it on something that many people don't agree is "essential" in any way. Putting the price aside just for a second, are there really people out there who think that code signing isn't worthwhile? Remember paint.net/filezilla having ad links to "Download Now" that would download... not paint.net or filezilla?
- ChrisSD 3y agoCode signing wouldn't necessarily fix that. There are a lot of "legitimate" applications that a user wouldn't want. For example, spyware is fine if there's some plausible deniability to it because many applications do some form of spying nowadays.
- solarkraft 3y agoYeah, me. It ensures that the binary you have is really from who it claims to be from, which can also be ensured by acquiring it through a secure channel (e.g. an HTTPS-enabled website or package repository). It doesn't give you any guarantees about the binary being free of malware - only that it's really published by the entity you got it from. Granted: Now an actor who wants to inject malware has to hijack the build process rather than only the website, but somehow I'm not convinced that's worth 600$/year and a lot of technical effort that could be put into securing the distribution chain.
- deleted 3y ago[deleted]
- kenjackson 3y ago$600/year buys you how much you can put into securing the distribution chain? 3 hours of dev time? If you can’t put $600/year into signing your binary, I don’t know how much effort you’re going to put into securing a distribution chain.
- michaelt 3y agoSo you're donating $600/year to ImageMagik for them to get a code signing certificate, right? Oh, you're not? Then why should the volunteer developers do so?