Software is subject to copyright. Yes you can implement the same APIs, but when you get into the visual presentation, things can get copyright related even if the code isn’t being ripped off.
If you decompile rather than clone, well then the code is copyrighted even if transformed into plausible source code.
The way I unterstand it, at least in European practice, the code itself is copyrighted, as in, the actual text, not the concept behing it. Decompiled source is not the same as original source, it goes through rounds of compiler optimisations and the process of reversing that includes a lot of guesswork. So, in practice, decompiling and working on the decompiled source was at least tolerated, probably because it would have been a grey area at worst.
In terms of whether the ‘clean room’ approach is as critical in Europe or not, I can’t be sure. It might be more permissable for someone to use a decompile as a reference and also directly work on a replacement. However I’m pretty sure starting with a decompile of proprietary software as a direct codebase would run afoul of issues.
Otherwise, imagine you have an HEVC encoded rip of a 4K blu ray. You transcode it to AV1. The bytes are totally different, and even the resultant frames are likely not even pixel for pixel identical. I don’t think copyright law would deem that not a violation, regardless of jurisdiction.
Transcoding would not be a violation, but in order to rip it in the first place, you had to bypass technological restrictions built into the disc and the drive. Under section 1201 of the DMCA, the creation or sharing of software that can do thatis a felony punishable by half a million dollars and six months in prison for a first offense.
Resharing your transcode would be a violation, even assuming the original was somehow an unencumbered HEVC. Ripping a VHS and encoding would still be a violation even without any DMCA complications
I am not a lawyer, this is not legal advice, as should be obvious by me being a random dude on the internet.
you can kind of sue about breaches of contract, but that’s civil law, not criminal law, so not illegal
unless I profit from that or use it to defame <redacted>, they might have a hard time demonstrating their damages from that breach
I didn’t sign any contract with <redacted> over their firmware anyway, and it will be hard to prove for them that I did, so kiss my ass
I’m not in the US, neither is <redacted> so the DMCA can kiss my ass as well
there are people who do this kind of work above-board, mostly in academic contexts, with their name attached to it, and as far as I can see they still walk around freely
you might want to double check your country’s laws. back when the DMCA was first passed the US was also in talks with a bunch of other nations and sneakily made it a condition of doing any trade with the US that they had to adopt basically a copy paste of the DMCA. if you’re in Canada for example it’s called the Copyright Modernization Act. If you’re in the EU it’s called CISD 2001.
Reverse engineering isn’t illegal. It’s how projects like Wine are possible.
Well, depends.
Software is subject to copyright. Yes you can implement the same APIs, but when you get into the visual presentation, things can get copyright related even if the code isn’t being ripped off.
If you decompile rather than clone, well then the code is copyrighted even if transformed into plausible source code.
Of course then there are patents…
The way I unterstand it, at least in European practice, the code itself is copyrighted, as in, the actual text, not the concept behing it. Decompiled source is not the same as original source, it goes through rounds of compiler optimisations and the process of reversing that includes a lot of guesswork. So, in practice, decompiling and working on the decompiled source was at least tolerated, probably because it would have been a grey area at worst.
In terms of whether the ‘clean room’ approach is as critical in Europe or not, I can’t be sure. It might be more permissable for someone to use a decompile as a reference and also directly work on a replacement. However I’m pretty sure starting with a decompile of proprietary software as a direct codebase would run afoul of issues.
Otherwise, imagine you have an HEVC encoded rip of a 4K blu ray. You transcode it to AV1. The bytes are totally different, and even the resultant frames are likely not even pixel for pixel identical. I don’t think copyright law would deem that not a violation, regardless of jurisdiction.
Transcoding would not be a violation, but in order to rip it in the first place, you had to bypass technological restrictions built into the disc and the drive. Under section 1201 of the DMCA, the creation or sharing of software that can do thatis a felony punishable by half a million dollars and six months in prison for a first offense.
Resharing your transcode would be a violation, even assuming the original was somehow an unencumbered HEVC. Ripping a VHS and encoding would still be a violation even without any DMCA complications
That is explicitly prohibited by virtually all proprietary software license agreements.
Which makes it a breach of contract, but not illegal.
I have news for you about breaches of contract. They can be sued over.
Also DMCA 1201 is a thing which often makes reverse engineering a felony.
I am not a lawyer, this is not legal advice, as should be obvious by me being a random dude on the internet.
you might want to double check your country’s laws. back when the DMCA was first passed the US was also in talks with a bunch of other nations and sneakily made it a condition of doing any trade with the US that they had to adopt basically a copy paste of the DMCA. if you’re in Canada for example it’s called the Copyright Modernization Act. If you’re in the EU it’s called CISD 2001.