My open source Android hardening project had already been renamed to the Android Hardening project when hardened_malloc was developed and released.
The hardened_malloc license requires attribution. License and copyright header needs to be included by anything using the code.
Conversation
Copperhead is misrepresenting my allocator hardening work throughout the years as their own. They're fraudulently misrepresenting my open source work throughout the years as their own and by not complying with the licensing. This is a particularly egregious case of it though.
1
1
18
I have never been an employee of Copperhead. There was never any employment agreement or salary. They made retroactive changes claiming I was an employee in 2017 and early 2018 before pushing me out. Even if that was true (it's not), this work was not done in that time period...
1
17
Copperhead also fraudulently claims to have upstreamed code in AOSP, which is not the case. I landed changes in AOSP as an individual. I explicitly signed the CLA with Google as an individual. They also falsely claim credit for work done entirely by Google with no coordination.
1
15
Similarly, they've tried to imply that they have involvement in the Seedvault project which is not the case. They've made no contributions to Seedvault. It was created by Steve Soltys and has done the bulk of recent development. Copperhead has no involvement.
1
15
My involvement in Seedvault was coming up with the concept and inspiring the author to create it. Calyx stepped up to help get it past the finish line to a stable release and is continuing to make substantial improvements. This is a team effort, not involving Copperhead at all.
1
15
Copperhead continues to claim credit for work done by others. They also falsely claimed that Calyx and many other organizations were their partners when it wasn't the case. They've removed those claims, but they continue to make these kinds of false claims. The fraud never ends.
1
13
This Tweet was deleted by the Tweet author. Learn more
This Tweet was deleted by the Tweet author. Learn more
This Tweet was deleted by the Tweet author. Learn more
You should only use the latest release. There are no supported older releases with security updates, and there were substantial privacy security improvements in Android 11. I'm just explaining that Copperhead doesn't understand these basic details of the OS they claim to harden.
This Tweet was deleted by the Tweet author. Learn more
By the way, I made a typo in the previous thread and decided to correct it so I had to repost all of the tweets following the one that I edited. That's why the tweets above are shown as deleted.