This doesn't sit right with me. I don't find @matthew_d_green's gut feeling that this person was part of a government scheme to backdoor cryptography to be a valid reason to send a mob after them 12 years later. They aren't even the main author of this.
The information security community gives the benefit of the doubt to a lot of people who in the past compromised organizations and users.

In this case, we don't know she did that, and even if we did it's not like she was maliciously hacking people and dumping their mail spools.
Assume that there is really an elaborate backdoor. There's enough circumstance evidence to believe it. The Extended Random feature by itself isn't a backdoor:



I think the fact this person attached their name to it publicly hints they may not have known.
I don't think there's the evidence to justify publicly accusing this person of knowingly being involved in creating a set of standards usable together as a backdoor. There's a difference between accusing the NSA of doing it and singling out a person they had do standards work.

• • •

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

7 Feb
@FiloSottile @JulianWasTaken He did this to @renlord1 because he helped with porting my open source work on hardening Bionic libc to a newer version of Android. The work was published under open source licenses and I'm the author and owner of it. Copperhead agreed to sponsor my work under those terms.
@FiloSottile @JulianWasTaken @renlord1 It's possible to look at archives of it on GitHub and see that it was published that way. I temporarily re-licensed my work under a non-commercial usage license from January 2017 to around June 2018. I never assigned copyright to the company, and my project predates the company.
@FiloSottile @JulianWasTaken @renlord1 Their position is that they somehow magically got copyright ownership over the entirety of my past, present and future work without any agreement of that kind. It goes against the explicit agreements we had that developers owned their work. That is what we told people too.
Read 4 tweets
7 Feb


Copperhead has repeatedly threatened open source developers and used underhanded methods to try causing harm to them. At the same time, they depend entirely on the code we're writing and continue taking it. I hope that people stop funding these attacks.
They're trying to cause serious harm to people for daring to improve open source software. They forked our software and sell a very flawed version of it with tracking and far less hardening as a closed source product. They see the original project as a threat to their scamming.
This is far from the only person Copperhead has tried to intimidate and harm for contributing to open source software. They target people based on what they perceive as their vulnerabilities. Don't fall for their CEO trying to make himself out to be a victim. He's a sociopath.
Read 5 tweets
3 Feb


Copperhead is still squatting on these domain names. GrapheneOS was formerly known as CopperheadOS and we used that name for the project before the company existed. This name was adopted afterwards. They have no valid reason to be using it...
Maybe it's time to make another attempt to get @Twitter to return the open source project's Twitter account.

Copperhead tricked Twitter into letting them hijack it by reversing an email change months earlier away from daniel.micay@copperhead.co when I stopped trusting James...
To be clear, I'm talking about the project's previous Twitter account, not the new @GrapheneOS account created as a replacement for it. I created this personal account as the initial replacement for it in June 2018 after the original project account was hijacked by them.
Read 4 tweets
3 Feb


This is so tiring. Don't get a single day without multiple serious attempts to harm the project by Copperhead and their associates. They reach out to tons of people trying to trick them with their false narratives in private. They threaten contributors.
They don't seem to get that they're never going to succeed at destroying the project. Considering that they're still copying our code, documentation and even things like tweets it's really not sure what they are trying to accomplish. They're nothing without our code and research.
In response to GrapheneOS getting more attention, they're ramping up their attacks. The privacy and security industries are full of these charlatans building businesses on dishonest marketing and harming others. This is such an extreme case. They're so invested in harming us.
Read 12 tweets
3 Feb
@CitadelHyperion @GrapheneOS It's a good comparison. The privacy and security industries are full of charlatans / scammers. James Donaldson (Copperhead CEO) is one of them. He's a narcissistic sociopath obsessed with causing harm to us in any way possible. He's obsessed with harming us in any way he can.
@CitadelHyperion @GrapheneOS He finds people he can trick, just like Craig. He gets sponsored reviews and content published by people that are trusted by others in the cryptocurrency community. Buys them phones, brings them into his business as resellers, etc. That's how he's getting resources to harm us.
@CitadelHyperion @GrapheneOS They sell a poor clone of our work with tracking for license enforcement for a huge amount of money. That money largely goes to bogus legal attacks and further promoting it in the same way. They're getting increasing desperate and are constantly spreading misinformation/attacks.
Read 4 tweets
30 Dec 20
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.
Read 13 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!