6 ms·
It’s astonishing that a project as critical and widely used as ImageMagick can’t even scrape together $629 for something as essential as a software signature.
by keepamovin 3y ago
It’s astonishing that a project as critical and widely used as ImageMagick can’t even scrape together $629 for something as essential as a software signature.
It’s a glaring example of how the tech industry fails to financially support the very open-source projects that it relies so heavily upon.
Despite offering incredible value, these projects often can’t capture enough of it to sustain themselves.
It’s a sobering reminder that something significant needs to change in how we approach and value open-source contributions.
- rand846633 3y agoIt’s also not clear why the IM project should be paying MS and not the other way round…
- lodovic 3y agoBut that's a thin line. Free certificates negate security. Instead, there are various foundations that sponsor popular open source projects for costs like signing certificates and hosting. I'm sure one of these should be trustworthy enough to obtain a signing certificate themselves so they can issue and revoke certs to various projects without much cost.
- sime2009 3y agoLook at it this way, why should a project like IM pay MicroSoft for the privilege of enriching and adding value to the Windows platform?
- layer8 3y agoThe fee for code signing certificates doesn't go to Microsoft.
- sime2009 3y agoWho actually receives the money is not relevant to my core point.
- kenjackson 3y agoIf it’s not relevant to your point, can you make your point without stating something that is false?
- sime2009 3y ago"Look at it this way, why should a project like IM pay anyone for the privilege of enriching and adding value to the Windows platform?"
- kenjackson 3y agoThey aren’t adding value to the Windows platform, unless you consider any application is adding value to the platform it is running on. In which case why should one pay for dev tools, their dev computer, libraries, art assets, etc…
- rat9988 3y agoBecause Ms hasn't asked for it.
- sime2009 3y agoOf course MS asked for it. They created and sustain this situation where software needs to signed for it to easily run on the Windows platform. Who do you think put the signature checking code and root keys in Windows?? The code signing gnomes?? fairies??
- justinclift 3y agoSeems more like the work of gremlins or devils. ;)
- 3y ago
- kergonath 3y agoThis does not solve the problem at all, and does not improve security either. Microsoft themselves could perfectly well have the same analysis in-house and provide free certificates to properly vetted projects. Adding layers of middlemen to deal with is a pain in the backside and a consequence is that some projects will just not bother. It’s inefficient on all levels and still does not protect from bad actors.
- mike_hearn 3y agoThey practically do. Distribute via the MS Store and they'll sign your software using Microsoft keys, and it costs you $19 once. It's the best way for ImageMagick to resolve their cost issue.
- deleted 3y ago[deleted]
- vasdae 3y agoMS does not sell certificates.
- Zuiii 3y agoIt's the one mandating them and not offering acceptable alternatives.
- pl4nty 3y agothey do offer an alternative, Azure Code Signing (ie cloud HSM). ImageMagick are looking at moving to it. it's free but someone difficult to access, due to the identity verification requirements
- gloosx 3y agoThe cartel leaders don't sell drugs, street pushers do. MS just have to sell licenses to sell certificates.
- keepamovin 3y agoYeah, I mean people should definitely be paying ImageMagick. Or perhaps it's more true to say, "ImageMagick should definitely figure out a way to become a business."
- serf 3y agoyou see it as a failure of the tech industry to finance open source. I see it as a failure to provide security systems like this without the need for financial gatekeeping. $629.00 isn't a trivial amount of money.
- megraf 3y agoConsidering the scale of ImageMagick- $629 is a very, very small amount of money considering the value that IM has generated.
- CogitoCogito 3y agoHave you considered volunteering to pay for and run the signing infrastructure?
- keepamovin 3y agoThere's a better way to see this: once can make a statement about the principle of the necessity of having transactions to exchange value, but not have a particular demand for the offered good or service themselves. I think that's what's going on here, so it might be better to keep these seeming "gotcha" type questions, which are irrelevant, either out of the discussion, or at least remember how they are misplaced! :)
- CogitoCogito 3y agoMine wasn’t a “gotcha” question. If the poster’s answer is “no” (i.e. that they don’t want to pay for or run such a system), then maybe they should consider that the same applies to everyone else.
- keepamovin 3y agoThat's the definition of a "gotchat". Yes: problem solved, no issue. No: problem solved, no issue. Ha, gothca! Hahaha :) Thanks for the laugh, pal. I'm outta here fer now! :) ;p xx ;p
- pentagrama 3y ago$629/year
- keepamovin 3y agoSure. Yep that’s what i meant. 629/yr. It’s travesty they can’t afford it. Can’t edit now. Thank you for clarifying!
- 0x000xca0xfe 3y agoThey surely can afford it, they just rather spend it on more meaningful things. Like taking out your entire family for dinner, having a developer meetup or whatever they do with their own money. You seem to be both interested in ImageMagick and having certified binaries, why don't YOU pay it?
- keepamovin 3y agoIt seems you feel incredulous that I suggest companies and individuals should be rewarded for the value they create, but that I don't want to pay it myself in this case? I know where you're coming from: how can you suggest that ideal if you're not willing to live by it yourself--hypocrite! discard the rest of what this person says. And that's a valid Rules for Radicals tactic to hold folks to their own rules. However, where I think you misunderstand in this case, is I am arguing for a principle, I don't have a need of a licensed ImageMagick Windows binary in this case. My comments make it clear that I'm discussing the wider issue of exploitation in OSS. This issue itself will not be solved by me chartiably bailing out a struggling project based on a general principle. In fact, such charitable expectations go against the solutions I propose. Instead, the solution I advocate for in my comments here is: bring easy transactions to open-source. But if we are being overly glib and misrepresentative, then permit me my own inaccurate and irrelevant misrepresentation of you as hypocrite, too, please--for fairness of course: why don't YOU act entitled and demand free features that you "really need" but you never intend to pay for, then a throw a tantrum when they are declined? You see how that tac doesn't really work? I'm sure you're not actually like that. Just as you should be sure I'm not in fact like you wish to merely pretend. Generously, at least you should assume I'm not! :) Anyway, aside from such lightweight guerilla shots, do you have anything substantial to contribute to this discussion? I feel you do and eagerly await it, if you channel your passion into a sharp and perceptive comment! :) -- So let's start over with some analysis of whether they can afford it or not: > "Surely they can afford it but wish to spend on other things." Your statement implies they can't actually afford it, since they opt to allocate funds elsewhere. The opportunity cost appears too high for them. > "But a certificate there would cost $629 (tax excluded) for a single year. If your organization requires a signed installer then please consider sponsoring us with a code signing certificate." The GitHub announcement use of "but" and the immediate call for sponsorship suggest that the $629 price is, in fact, a financial hurdle for them. Suggesting, contrary to your claim, that they cannot, in fact, afford it.
- 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."
- midasuni 3y agoFree Software is about freedom. Not paying rent to Microsoft or their partners.
- keepamovin 3y ago"Freedom for whom?" For the developers whose time they invested. For the users who are not "free" of their problems that prompt them to see these "free" solutions? Nothing about OSS is free. "Free" is a lie. Pernicious, in that it was passed off under the guise of some ideal, yet it undermines the long term sustainability of the field by supporting a sense of entitlement.
- eesmith 3y agoYou are getting tangled up by the two different meaning of the word "free". Quoting https://www.gnu.org/philosophy/free-sw.en.html https://www.gnu.org/philosophy/free-sw.en.html > “Free software” means software that respects users' freedom and community. Roughly, it means that the users have the freedom to run, copy, distribute, study, change and improve the software. Thus, “free software” is a matter of liberty, not price. To understand the concept, you should think of “free” as in “free speech,” not as in “free beer.” We sometimes call it “libre software,” borrowing the French or Spanish word for “free” as in freedom, to show we do not mean the software is gratis. The four essential freedoms are: * The freedom to run the program as you wish, for any purpose (freedom 0). * The freedom to study how the program works, and change it so it does your computing as you wish (freedom 1). Access to the source code is a precondition for this. * The freedom to redistribute copies so you can help others (freedom 2). * The freedom to distribute copies of your modified versions to others (freedom 3). By doing this you can give the whole community a chance to benefit from your changes. Access to the source code is a precondition for this.
- keepamovin 3y agoNo, I am not tangled in it, I'm aware of it. I think you may be tangled in "free software" orthodoxy tho, and confused by it! :) Moreover, I am reflecting the confusion between free as in price-free and free as in restriction-free in the original comment. Ergo: "FS is about freedom" suggests restriction-free. "Not paying rent" suggests price-free. I am also suggesting the FS dogma is deceptive, and clouds the issue. You will do well to think more deeply of these things, instead of simply quoting from a FS site. Please go back and read my original comments to which you are replying. The meaning may be in there to set you free from this! :)
- blueflow 3y ago... having to pay $629 just to ship a thing you made for free? I refuse to accept this as a normal thing to do. Microsoft inflicted this upon the Windows ecosystem themselves.
- keepamovin 3y agoYet you didn't really make it for "Free". That's part of the lie (innocent here surely) that developers time is "limiteless and cost free". Lies such as these lead to and support the abusive and exploitative sense of entitlement that many, unfortunately, take towards OSS. It's costs are many. If you have a more humane bent you will consider the psychological toll, and note the many "I'm leaving OSS" posts one can observe. If you have a different bent you may appreciate the more economic cost incurred by this lack of market efficiency: an exploitative market that fails to ensure commensurate exchange of value does not have much future. At best, "cost free" OSS is a short-term play, murkily backed by the same "robber baron" attitudes than underpin the exploitation of workers (and the gaslighting of the whole class to believe they can expect nothing more), throughout human history. Let's not permit OSS to go down this sad, tired and disastrous path. You can't grow the productive output of a market unless you respect property rights and exchange of value.
- blueflow 3y agoI did make it for free. And i expect no recognition or profit. I did my OSS contributions for my own usecases and sharing the fruits with the public is a neat side effect. Also your hyperbole is apalling.
- keepamovin 3y agoThe only appalling hyperbole is you trying to sneakily misrepresent the above as hyperbolic! :) > I did make it for free. And i expect no recognition or profit. But you didn't make it for free. Your time is not free. The resources you use are not free. What you expect, is, to put it lightly, flexible. Your expectations change as you gain understanding and experience. Perhaps you're fond of RPGs? Like that. > I did my OSS contributions for my own usecases and sharing the fruits with the public is a neat side effect. Plenty of businesses began the same way.
- doubloon 3y agouniversal basic income?
- keepamovin 3y agoDoesn't capture enough value. Not proportional to creative output as it should be. Fair idea for just general living, everyone should receive that. But, if you create value, you get rewarded. Capitalism FTW
- ogurechny 3y agoIf you frame it as “just” the money problem, you are suddenly competing with everyone who has more money, and they can surely win in that. If you frame it as “security” problem, you are already nothing compared to those who are believed to have the final say on “security”. Before you play, remember that the house always wins.
- keepamovin 3y agoHa! Your username is hilarious. Have you seen those cat-cucumber videos? What is up with that?? Hahaha :) Thanks for your comment; it's certainly thought-provoking. You're advocating for a more strategic look at the challenges open source projects face, which I appreciate. Also, I like your "Socratic"-style! :) Firstly, you mention that framing this as a "money problem" pits us against bigger players with more resources. While that's a concern, the idea that you can't succeed if you don't already have money is fundamentally flawed. Every large business started small. In the realm of open source, financial challenges aren't unsolvable; they require a new transactional approach. On the security aspect, yes, established authorities have a stronghold, but that's not unbreakable. Look at services like Let's Encrypt, which offers free SSL certificates at scale. They emerged as a disruptor, challenging the established norms in a market that was seemingly locked down. And to your final point, about "the house always wins," I'd say this defeatist attitude is the real obstacle. The notion that we can't or shouldn't try to change the system is harmful. You say the house always wins, but who exactly are the "insiders" here? Are we just supposed to accept the status quo, or should we aim for innovation that could make the system more equitable? So, back to you: what solutions do you see? Or at least, what approach do you think has a fighting chance? I'm genuinely curious to hear your perspective.
- ogurechny 3y agoI didn't mean that you “can't succeed” or “can't win”. You can, but the process itself silently changes, and you are now playing by others' rules instead of your own, and get concerned with goals that are different from the original. The idea that you need to “succeed” or “win” itself is something others told you. Power does not always come with fear, it can be unnoticeable or hidden inside candy wrapping. An existing person does not exist to corporate/government structures without official papers proving it. In the same manner, users can't access many modern services without social network account or mobile phone number (which is a qualified long term tracking id which allows these services to find their place in existing data trading schemes). Smartphones essentially belong to platform owners which merely allow consumers, hardware, and application makers to use their services. The problem is not whether “A is good” or “B is bad”, the problem is giving those abilities to decide to some entity, which people do voluntary. The idea is that you shouldn't play with a swindler at all if you understand that it's a swindle, even if inertia or goading makes it the easier choice.
- wredue 3y agoStep one would probably be to stop the incessant shitting on everyone that suggests source available developers do, in fact, have a right to find ways to extract value out of their code, and that the OSI is probably the cause of all the funding woes. But since we’re still not past even this after YEARS, I have little faith that we’ll ever get there.
- keepamovin 3y agoIt's clearly an impassioned topic for you, but it's important to remember that your passion may be clouding your judgement. While indeed methods exist, many problems remain, and it's useful to note that not all systems currently used may be appropriate for all creators. Your suggestion that complaints about current solutions are invalid, implies a lack of empathy with those who aren't served by existing mechanisms. This view could come across as too one-sided, which might hamper its ability to be taken seriously. Similarly, your comment seeks to curtaIl any critic of OSI licenses, and while it's true they provide many protections and benefits, it's also true that many new licenses and mechanisms are being used as a result of gaps in the current approach. Failing to understand the concerns of other segments of the ecosystem with which you may not be acquainted, does not mean their complaints are without merit. You may take it as an opportunity to better grasp the realities facing creators to give you a clearer understanding of the issue overall.
- keepamovin 3y agoI have a point I wish to add that doesn't neatly fit in reply to anyone else, so I'll just reply myself, here: Restricting the meaning of the word "free" to one defined by "FS" orthodoxy, is very not free, wouldn't you agree? Haha :) Indeed the word free has many meanings, and consequently care must be taken to avoid confusion. Defining free in a way that only aligns with a particular ideology may be seen as self-serving, or confusing and deceptive. It's important to avoid such biases in order to clearly examine the real issues. It's understandable, given the dependency of big business on price-free software, that business would not want the "price-free" nature of much software to change. A "price awakening" among creators would directly threaten the bottom lines of these companies. Unfortunately, it seems they are also abusing the ideology of "FS" to create confusing false notions of a "noble software creators who gives away their creations without extracting any money". This is abusive, and exploitative, and it must stop. The way it will stop will be creators waking up. The way they will wake up will be thinking clearly, not simply subjugating themselves to, or repeating, misapplications of "FS" ideology. Specifically, my commentary here seeks to expose the costs that occur throughout the lifecycle of software creation, and avoid the confusing false equivalences with "FS" ideology. It is by hiding or ignoring those costs that exploitation of creators is permitted to flourish. Training creators to think in ways that do not account costs to their time, or to their creations, or, that make it unacceptable to do so, is abusive. It's a gaslighting mindset that seeks to prevent creators from capturing the value they have a right to. It's important to avoid deliberately misusing the idealism of a "FS" movement to suggest money should not be exchanged, as this is abusive to creators. Deliberate blurring of meanings, and the creation of false equivalences and reductions, is deceptive tactic is designed to confuse in order to prevent clear understanding of the issues. This in turn can hamper people asserting their right. In this context, the ideology of the "FS" movement, is often used to create a confusing equivalence with price-free. This in turn suggests there virtue in not requesting payment for software. Overall, this abuse of "FS" ideology is done in order to continue to exploit creators. In short, the very ideology of freedom you tout is abused as to restrict creators, and oppress their right to financial self-determination. And the "FS" movement is misused in this way to create an ideological fake justification for not capturing value from software. It's important to not participate in the perpetuation of such harmful lies and misuses of principles. While the ideologies of free software are commendable, they must not be used to repress the freedom of creators to earn from their creations, as is attempted to be done with the line of argument espoused in your comment. It can be difficult to see people earning from their creations, and it's understandable to have fear that you will not be able to afford software if this idea of charging for it spreads. However, it's important to understand that the current situation is abusive and must be terminated. Exploitation is not sustainable, and the software economy must respect the rights of all participants in order to be just. I challenge folks to advocate for a more positive and inclusive stance on this issue, that supports creators and clear thinking about the issues involved! :) Dispelling muddy thinking must be a top priority of anyone who aligns with that, and to that end, I encourage you all to re-evaluate your injection of "FS" points into these moments. :)