Security through obscurity is not security. The algorithm for SHA-256 is publicly available, doesn’t mean that you can use that knowledge to reverse the 1 way cryptographic encryption on it, nor can you brute force it with the computation power of the equivalent of 37 observable universes from big bang to heat death.
Security through obscurity is how you get the eMudhra 4 incident.
There are no examples where obfuscation of code is an inherently good thing (except to hoard knowledge for profit motives). I use Blender, the FOSS 3d software that at this point, easily competes with and even imo, outperforms established proprietary closed source software and has a plugin community so robust that if thers is something in another program that isnt in blender, its very likely someone has made an equivalent as a, often free, sometimes paid plugin that does the thing. Were also at the point where the proprietary software has been taking design cues from Blender and applying them to their own proprietary programs.
I would want to know that my bank is using SHA-256 to encrypt passwords and my information.
In general, I have an issue with the notion of “intellectual property”. There is no reason to restrict what is essentially knowledge. I’d even argue it’s dangerous in many cases. Also, it’s absurd because you are never the only person having the same idea, yet people are being punished for not publishing it first.
As for the bank example - I am not. Opening the code does not mean everyone has suddenly access to your data. Your data is hopefully encrypted well … which you will never know, because your bank keeps everything hidden from you. No possibility for you to make an informed decision, based on your own research or that of experts.
That’s a perfect frame for hackers to operate in. It’s also a perfect frame for companies to cut corners and reduce costs, while getting the maximum amount of money out of you.
In general, I have an issue with the notion of “intellectual property”
As a broad economic policy - providing an economic incentive to create IP is very good. It is was fueled nearly all of the innovation of the last 300 years, probably longer. It also has downsides, but it is a net good. I firmly do not think there would be as much advancements in general if we structured IP in a way that was public / no profit motive.
Opening the code does not mean everyone has suddenly access to your data
No but it means your exact package dependencies are public. Your exact encryption methods are public. The specific ways the data is distributed is public. And so on. This makes it significantly more vulnerable to the various attacks which would lead to leaked data.
No possibility for you to make an informed decision, based on your own research or that of experts
Is there a name for this fallacy? The “Your own research outweighs that of a trained team of professionals” part. Me conducting the research does guarantees intent alignment; it does not guarantee accuracy. I’m wrong about things all the time.
The idea that some random bloke, even a trained software engineer, could look at the massive legacy repositories of these banks and make an “informed decision” is silly. I guess if there was glaring flaws, then maybe. But realistically, most people would just rely on a handful of organizations to audit the repo’s and summarize the security for me except… those sorta already exist. Via things like SOC 2 and what not. Even a trained security specialist spending many months full time dedicated to evaluating the security of the bank (based on their open sourced code) would have a hard time coming up a decision.
For the most part in humanity’s existence, innovations didn’t depend on arbitrary rules of lockdown and monetary incentive. Sure, it helps, I’m not questioning that, but I don’t see why in an open source society this would have to stop. I have a problem, I’ll give you money to solve my problem. When you’re done, open up the code. Why wouldn’t you take the job? Why wouldn’t I still pay for work/help?
As for the second part, there is a lot of security related software which is open source that is still secure, I’m not talking fringe cases, I’m talking industry standards - encryption being on the forefront. Or rather BECAUSE it is open, it is so secure. The method of how you do things, does not enable others to crack the result you have in the end. For instance, we know exactly how some VPN tunnels are being encrypted. Cracking this encryption live though is a whole other story.
Third part. Correct, you can never be 100% certain. Doesn’t mean this is a fallacy. The chance of catching holes in the system rises dramatically with the amount of persons checking said system. You want a fallacy? Then riddle me this. Why would someone trust a company obfuscating its method and selling a ‘trust me bro’ more than multiple (cross-)checks done by thousands of independent individuals all over the globe?
The people I’m providing my service to do indeed get this service for free. But what has that to do with open source?
I already wrote you don’t have to make money with code. You can offer support and be payed for that, or you offer to fulfill feature requests.
Or you can bind a license to your code if you absolutely want to squeeze something out of it. Just because a code is open doesn’t mean that you have to publish it under a license that allows for free use. You know the funniest part of this? If every code was open, it would also be very easy to proof that someone used your code or parts of it illegally (according to your license).
I guess the key is that ‘open source’ generally means ‘free use’ versus ‘source available’ which at least in the old days used to be a supremely common arrangement for commercial software.
I will also agree that every other IP pretty much is effectively ‘source available’, you see a book, there’s no hidden secret form you need to construct that work. Nothing inherently stops you from reproducing a modified copy. Sure there are more convenient assets (having distinct tracks that are used to compose a song versus only the post-mix recording), but generally other IP has to decide how to deal with remix, sampling, etc, without some fundamental barrier like ‘it got compiled into machine code which is hard to modify’.
Well I understand the justification for human produced code not being open source. It could have taken them, hundreds of hours, depending on the program, to develop. They need to be compensated for that time.
But AI, it can recreate Photoshop in a day and it’s not even as if anyone had to sit and stare at the screen the entire time. That being said it’s not resourceless, somebody has to pay for the power it took to generate so even AI produced code probably should cost something but not anywhere near as much as human produced code electricity is a lot cheaper than human time.
Let me rephrase that. In an ideal world we would open every code. You still can make money with support or feature requests and so on. It just would make everything more resilient and easier to fix. Having said that, we’re not living in an ideal world, so this will remain a philosophical debate forevermore.
As for the AI part, if I’m playing advocate of the devil here, energy costs are one thing. The other is, forging the prompt and iterating on it still needs humans. There is work in this process that can be worth a compensation.
So, would you say open up the AI code, but allow for the prompting to be “closed source”?
All code should be open source, period.
Absolutely insane, terrible take.
Code is intellectual property just like anything else. You should be able to make something and then decide who can use it and under which conditions.
And I’m pretty content with my banks code not being open sourced.
Security through obscurity is not security. The algorithm for SHA-256 is publicly available, doesn’t mean that you can use that knowledge to reverse the 1 way cryptographic encryption on it, nor can you brute force it with the computation power of the equivalent of 37 observable universes from big bang to heat death.
Security through obscurity is how you get the eMudhra 4 incident.
Yes yes I know. I was just making a list of the top of my head, you win the technical point that this specific example isn’t great.
There are no examples where obfuscation of code is an inherently good thing (except to hoard knowledge for profit motives). I use Blender, the FOSS 3d software that at this point, easily competes with and even imo, outperforms established proprietary closed source software and has a plugin community so robust that if thers is something in another program that isnt in blender, its very likely someone has made an equivalent as a, often free, sometimes paid plugin that does the thing. Were also at the point where the proprietary software has been taking design cues from Blender and applying them to their own proprietary programs.
I would want to know that my bank is using SHA-256 to encrypt passwords and my information.
In general, I have an issue with the notion of “intellectual property”. There is no reason to restrict what is essentially knowledge. I’d even argue it’s dangerous in many cases. Also, it’s absurd because you are never the only person having the same idea, yet people are being punished for not publishing it first.
As for the bank example - I am not. Opening the code does not mean everyone has suddenly access to your data. Your data is hopefully encrypted well … which you will never know, because your bank keeps everything hidden from you. No possibility for you to make an informed decision, based on your own research or that of experts.
That’s a perfect frame for hackers to operate in. It’s also a perfect frame for companies to cut corners and reduce costs, while getting the maximum amount of money out of you.
Yes there is: It creates a financial incentive to create new and better things. This is why patents exist.
As a broad economic policy - providing an economic incentive to create IP is very good. It is was fueled nearly all of the innovation of the last 300 years, probably longer. It also has downsides, but it is a net good. I firmly do not think there would be as much advancements in general if we structured IP in a way that was public / no profit motive.
No but it means your exact package dependencies are public. Your exact encryption methods are public. The specific ways the data is distributed is public. And so on. This makes it significantly more vulnerable to the various attacks which would lead to leaked data.
Is there a name for this fallacy? The “Your own research outweighs that of a trained team of professionals” part. Me conducting the research does guarantees intent alignment; it does not guarantee accuracy. I’m wrong about things all the time.
The idea that some random bloke, even a trained software engineer, could look at the massive legacy repositories of these banks and make an “informed decision” is silly. I guess if there was glaring flaws, then maybe. But realistically, most people would just rely on a handful of organizations to audit the repo’s and summarize the security for me except… those sorta already exist. Via things like SOC 2 and what not. Even a trained security specialist spending many months full time dedicated to evaluating the security of the bank (based on their open sourced code) would have a hard time coming up a decision.
For the most part in humanity’s existence, innovations didn’t depend on arbitrary rules of lockdown and monetary incentive. Sure, it helps, I’m not questioning that, but I don’t see why in an open source society this would have to stop. I have a problem, I’ll give you money to solve my problem. When you’re done, open up the code. Why wouldn’t you take the job? Why wouldn’t I still pay for work/help?
As for the second part, there is a lot of security related software which is open source that is still secure, I’m not talking fringe cases, I’m talking industry standards - encryption being on the forefront. Or rather BECAUSE it is open, it is so secure. The method of how you do things, does not enable others to crack the result you have in the end. For instance, we know exactly how some VPN tunnels are being encrypted. Cracking this encryption live though is a whole other story.
Third part. Correct, you can never be 100% certain. Doesn’t mean this is a fallacy. The chance of catching holes in the system rises dramatically with the amount of persons checking said system. You want a fallacy? Then riddle me this. Why would someone trust a company obfuscating its method and selling a ‘trust me bro’ more than multiple (cross-)checks done by thousands of independent individuals all over the globe?
What do you do for a living? What ever it is you produce, I want it for free.
The people I’m providing my service to do indeed get this service for free. But what has that to do with open source?
I already wrote you don’t have to make money with code. You can offer support and be payed for that, or you offer to fulfill feature requests.
Or you can bind a license to your code if you absolutely want to squeeze something out of it. Just because a code is open doesn’t mean that you have to publish it under a license that allows for free use. You know the funniest part of this? If every code was open, it would also be very easy to proof that someone used your code or parts of it illegally (according to your license).
I guess the key is that ‘open source’ generally means ‘free use’ versus ‘source available’ which at least in the old days used to be a supremely common arrangement for commercial software.
I will also agree that every other IP pretty much is effectively ‘source available’, you see a book, there’s no hidden secret form you need to construct that work. Nothing inherently stops you from reproducing a modified copy. Sure there are more convenient assets (having distinct tracks that are used to compose a song versus only the post-mix recording), but generally other IP has to decide how to deal with remix, sampling, etc, without some fundamental barrier like ‘it got compiled into machine code which is hard to modify’.
Hm, yeah, I guess the thought of ‘open source = free use’ is the issue that prevents many from entertaining the idea. Makes sense.
Especially now - let’s say you GPL some code - I have an LLM read it and write equivalent code but, so that each line is different.
Before you could put it out there, and ask “use this but give back.” Now it’s just “pretty please don’t steal from me. Just kidding, you already did.”
Well I understand the justification for human produced code not being open source. It could have taken them, hundreds of hours, depending on the program, to develop. They need to be compensated for that time.
But AI, it can recreate Photoshop in a day and it’s not even as if anyone had to sit and stare at the screen the entire time. That being said it’s not resourceless, somebody has to pay for the power it took to generate so even AI produced code probably should cost something but not anywhere near as much as human produced code electricity is a lot cheaper than human time.
Let me rephrase that. In an ideal world we would open every code. You still can make money with support or feature requests and so on. It just would make everything more resilient and easier to fix. Having said that, we’re not living in an ideal world, so this will remain a philosophical debate forevermore.
As for the AI part, if I’m playing advocate of the devil here, energy costs are one thing. The other is, forging the prompt and iterating on it still needs humans. There is work in this process that can be worth a compensation.
So, would you say open up the AI code, but allow for the prompting to be “closed source”?
hotter take but i’m right here with ya