Again, there is no issue here. What personal responsibility do I have to take?
Since the first GRE scanners that supported firmware updates (PSR-500), GRE and Whistler have tried to protect their intellectual property, keeping people from loading one scanner's firmware into another scanner. Since December 2016, you have released several versions of a utility whose sole purpose was to defeat those efforts.
http://forums.radioreference.com/gre-scanners/335862-dmr-nxdn-systems.html#post2623575
EricCottrell said:
GRE implemented a method that prevents loading the wrong firmware in the scanner
You acknowledged that what you were doing was intended to circumvent copyright:
http://forums.radioreference.com/gre-scanners/335862-dmr-nxdn-systems.html#post2623814
EricCottrell said:
The modify on-the-fly method is a traditional work around for distributing changes to copyrighted programs
Whistler apparently anticipated you releasing something that would circumvent their copyright (and potentially cause vocoder licensing issues) and changed their code to discourage such circumvention. With WS108x CPU firmware release 3.9 (Sept 2016) and later, if someone loads WS108x firmware on a non-WS108x scanner, they'll get no digital decode.
On 18 Dec 2016, you announced the release of your tool that circumvents GRE/Whistler's long-standing protections.
http://forums.radioreference.com/ra...loaded-whistler-dmr-firmware.html#post2683372
People quickly realized that using your tool to load any version of WS108x firmware 3.9 or later (current rev on that date was 4.4) results in loss of digital decode. They can back-rev to 3.8 and it all works again.
On 17 Feb 2017, you announced a release of your utility which defeats the protections Whistler added in 3.9:
https://forums.radioreference.com/r...ded-whistler-dmr-firmware-14.html#post2718793
EricCottrell said:
I fixed the experimental transcode function so WS-1080 firmware, up to Version 4.5, will work properly in the PSR-800, PRO-668, and Pro-18.
At best, that statement is incomplete. You didn't merely change the "transcode function"; you added code and data which modifies the Whistler executable and its checksum - the sole purpose of that change was to defeat the 3.9+ protections. Also, you're no longer "experimental" - the experiment was a success in December. Now you're just defeating more protections.
On 17 Mar 2017, Whistler released WS108x CPU firmware version 4.6. In yet another attempt to protect their property, Whistler encrypted the binary (in addition to both the "obfuscation" present in all firmware back to PSR-500 days and the protections in version 3.9 and later). People realize that they can't use your utility to load firmware 4.6. You clearly understood that defeating that encryption was likely illegal:
https://forums.radioreference.com/r...ded-whistler-dmr-firmware-18.html#post2734973
EricCottrell said:
It might be possible to work around this, but I have to tread carefully. People outside the US have more leeway.
On 20 Mar 2017, RR user n3617400 announces that he has removed the encryption Whistler applied to WS108x CPU firmware 4.6. He shares the resulting file:
https://forums.radioreference.com/r...ded-whistler-dmr-firmware-18.html#post2736744
n3617400 said:
hi everyone.
i'm convert the ws1080 cpu firmware 4.6 from new obfuscate form (524292 bytes) to old obfuscate form (368340 bytes).
https://www.filemail.com/d/nwyhwmtlufwpkci
can anybody check this firmware? i dont have pro-668. thanx.
While you're understandably reluctant to perform the decryption yourself, you're not at all hesitant to take advantage of Whistler's code once someone else has decrypted it. On 21 Mar 2017, you announce a new version of your utility, one which uses the 4.6 file above:
https://forums.radioreference.com/r...ded-whistler-dmr-firmware-18.html#post2737275
EricCottrell said:
I have not even tried to figure out the new obfuscation yet, since it is likely I could not distribute a program using the new method.
Since a firmware file with the old obfuscation suddenly was made available, I applied the suggested fixes and it seems to work. The changes have been committed and pushed. A new version of GREFWTool is available to support 4.6 in the old obfuscation format only.
On 27 Mar 2017, you acknowledged that one of your goals was to stay just barely on the "correct" side of the law:
https://forums.radioreference.com/r...ded-whistler-dmr-firmware-20.html#post2740557
EricCottrell said:
I have given some thought about adding the new code to the tool. I think it would open me up to more liabilities without much benefit. I have to tread carefully not to be part of the unintended consequences of US laws.
On 03 Apr 2017 you acknowledge that you at least recognize (if not respect) the concept of "intellectual property":
https://forums.radioreference.com/r...ded-whistler-dmr-firmware-20.html#post2744580
EricCottrell said:
Whistler is trying to protect their intellectual property.
And, despite knowing this, you still released several versions of a utility over 3 months - a utility whose sole purpose was to defeat such protections. (In anticipation of "it was just an experiment": Nonsense. If that was the case, the experiment was over in December 2016, when you demonstrated to the world that you could load Whistler's 3.8 firmware onto a PSR-800, PRO-18, or PRO-668 and the result would work just as well as a WS108x running 3.8. Continuing past that point, supporting versions 3.9 and later, went way beyond a successful "experiment".)
Back to your question above:
EricCottrell said:
What personal responsibility do I have to take?
From a purely legal standpoint, perhaps the answer is "none". Perhaps not.
Having worked closely with Craig for several years, I'm pretty certain he isn't referring to legal responsibility. I'd speculate that he's really talking about moral and ethical responsibility for creating a tool that defeats Whistler's various attempts at protecting their intellectual property. Responsibility for making such a tool available to the public. Responsibility for updating that utility every time Whistler makes improvements to their protections.