Copperhead registered the grapheneos.ca and grapheneos.net domains and redirected them to their site. I had my lawyer intervene and those redirects are now removed but they still have the domains. It's yet another example of their desperate attempts to harm us.
It's part of their continued attempts to fraudulently claim ownership over my work and to misrepresent themselves as the ones who created it. I started the project in 2014 before the company was founded in late 2015. The project has never been owned or controlled by Copperhead.
I created CopperheadOS before Copperhead existed. I never did that work for anyone but myself on my own time. It was formally agreed upon that I owned and controlled the open source project. Copperhead chose to ship the upstream releases of my project instead of making their own.
renlord.com/posts/2020-03-… is another example of their desperation.

They attempted to get a student contributing to open source software in trouble with university via fraudulent copyright claims.

They're regularly harassing GrapheneOS developers/contributions with these attacks.
It's verifiable that none of the CopperheadOS code was attributed to the company.

After pushing me out, they filed a fraudulent copyright claim over my work listing me as the author but falsely claiming that I had assigned copyright to the company. It's completely without basis.
Not only was there no copyright assignment to Copperhead but it was formally agreed upon from the beginning that I would own and control the open source project. I was only willing to work on it under that condition. It was regularly acknowledged that this was how it worked too.
Copperhead had 3 co-founders: myself, James Donaldson and Dan McGrady. McGrady was there for the incorporation agreement but left before shares were divided.

This is not a case of there people two people with different accounts of what happened. There are witnesses and evidence.
It is verifiable that GrapheneOS is the continuation of the original project and that the new CopperheadOS was created as a fork.

It's verifiable that it was published with attribution to me as author and owner. You can see they added bogus copyright headers when they forked it.


This code for secondary stack randomization was published in 2015 under the Apache 2 license. It was attributed to me as the author and owner. None of my work was ever done under any contracts or as an employee with a salary or any employment agreement.
I was paid out a share of the profit as a co-owner of the company, not as a salary.

Copperhead retroactively tried to frame it as a salary to get grants, to fraudulently pass along tax burden to me and as part of trying to take back agreeing to me owning my open source work.
There was never any contract for the work or any salary. There was no employment agreement or any amount that was determined to be a salary. There is no actual record of my receiving a salary. There were no pay stubs or anything like that because it wasn't what was happening.
They pulled the same kind of bullshit by retroactively going back and misrepresenting payments as shareholder loans.

They did that to roll the 2017 payments into the imaginary 2018 salary, where they conveniently said barely anything was withheld for taxes to pass that on to me.
Since they fudged the numbers to their benefit retroactively, there's no actual basis for any of that. There was no employment agreement and no salary so they just fudged the numbers. It was supposedly dividends until it suited their interests to retroactively change each year.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with DanielMicay

DanielMicay Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @DanielMicay

27 Dec 20
CAKE works extremely nicely for providing fair allocation of outgoing bandwidth from a server:

tc qdisc replace dev eth0 root cake bandwidth 500mbit besteffort

Bandwidth parameter needs to be properly set so that it becomes the bottleneck and actually shapes the traffic.
It will evenly divide the bandwidth between hosts so a host opening many connections (download managers) doesn't end up with higher bandwidth. It also evenly divides the per-host bandwidth between the flows to the host. SSH latency will also remain very low even under heavy use.
CAKE:

* client A with 1 connection gets 48mbit
* client B with 8 connections gets 6mbit each adding up to 48mbit

No CAKE:

* client A with 1 connection gets ~6mbit to ~16mbit
* client B with 8 connections gets ~6mbit to ~16mbit each adding up to ~80-90mbit

Stark difference.
Read 6 tweets
25 Dec 20


android.googlesource.com/platform/frame… is the place to start if you're interested in finer details of the implementation.

For Pixel 2 and later, isWeaverAvailable() is true.

SyntheticPasswordCrypto.personalisedHash(...) is used to quickly derive a value with SHA-512.
For example, the Weaver key is made by passing "weaver-key" and the password token to SyntheticPasswordCrypto.personalisedHash(...). That way, the password token derived with scrypt isn't actually sent to the secure element. That's used for deriving a bunch of different keys.
There's also other hashing that's not really noteworthy such as the lockscreen implementation hashing the password in a similar way before passing it along, etc. The actual work factor is provided by scrypt and the SoC-specific hardware-accelerated, hardware-bound key derivation.
Read 4 tweets
18 Dec 20
Copperhead has gotten back to raiding our IRC / Matrix channel. I'm sure they're probably also busy editing Wikipedia, reaching out to people to spread more lies, etc. Since they just poorly copy our code months later, it's not like they actually develop an operating system.
It really says a lot that this is how they spend their time. Going to be adding substantially more moderators on IRC / Matrix and Reddit. Also going to be taking a much more active approach to banning concern trolls. Would appreciate if other communities do the same with them.
Matrix has much worse moderation tools than IRC and is far more easy to abuse. It's unfortunate. Would be helpful to get in touch with matrix.org admins so that we could gain control of some aliases they registered via concern troll sockpuppets + some other things.
Read 4 tweets
5 Nov 20
github.com/GrapheneOS/har… was initially released in August 2018. I developed it to replace the port of OpenBSD malloc to Linux and Android that I made in 2014.

Copperhead was founded in late 2015 and split from my open source Android hardening project in June 2018.
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.
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.
Read 21 tweets
4 Nov 20
We need help building a more complete historical archive of the GrapheneOS code. Please get in touch with me if you have clones of the Git repositories from 2015 or earlier. The repositories on GitHub were the ones created for the CopperheadOS Beta but don't have older tags, etc.
There was an earlier generation of repositories for the CopperheadOS Alpha and earlier when the project was based on CyanogenMod, including before it was branded as CopperheadOS. It would be ideal to obtain an archive of this code. Obtaining this would make a big difference.
The network graphs like github.com/GrapheneOS/pla… and github.com/GrapheneOS/pla… show some of the forks of the project from the CopperheadOS Beta era. There were also forks in the earlier Alpha era and earlier. Ideally, we can get a full archive of it, not just specific repositories.
Read 5 tweets
1 Oct 20
@mamushi_io @intimitatem @Fonta1n3 @GrapheneOS You're just selling a proprietary project forked from our code in violation of the licenses. You're supporting a company that's anti-open-source and is waging a nasty war against the open source project they depend on. It's hard to take a proprietary ripoff seriously.
@mamushi_io @intimitatem @Fonta1n3 @GrapheneOS CopperheadOS is a fork of our legacy codebase in violation of the licenses with DRM and tracking added to the Updater app. It is primarily just AOSP with a custom boot animation and wallpaper, since they have not meaningfully maintained or developed real privacy/security work.
@mamushi_io @intimitatem @Fonta1n3 @GrapheneOS You're selling people a very expensive product that's making them less private and secure. The original open source project is available for free with far more privacy and security, and without tracking. People are far better off with iPhones than yet another 'secure' phone scam.
Read 5 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!