isn't copperos just a better version of graphene ? or I'm totally wrong ?
Conversation
No, CopperheadOS is a closed source fork of our legacy code.
GrapheneOS is the non-profit open source project created in 2014. CopperheadOS is a branded build of AOSP without substantial privacy and security hardening. It doesn't have current Android security updates either.
2
3
Now I am confused ? You worked for copperhead in 2015 and went to graphene in 2018? It existed in 2014?
1
GrapheneOS has existed as an open source project since 2014 and was based on my earlier work before that time. The project initially didn't have a name and was then known as CopperheadOS from a period in early 2015 to mid 2018. There are still changes around from 2014 / 2015.
1
1
I've never been an employee of Copperhead. I have never had any employment agreement or salary from them.
In 2018, after they stopped sponsoring the open source project, they claimed money sent to me that year was a salary but without any employment agreement or salary set up.
1
1
You can see our repositories on GitHub originate with the beginning of the project being based on AOSP rather than CyanogenMod:
github.com/GrapheneOS/pla
These are the repositories the project used since it was known as CopperheadOS Beta. The current 'CopperheadOS' is a fork.
1
1
And to be clear, it's a fork of our legacy code without our modern privacy / security hardening work, and without actually porting forward / maintaining the vast majority of the legacy work. The new 'CopperheadOS' is a branded build of AOSP masquerading as hardened. It's not...
1
GrapheneOS is not a company. I never 'went' to Graphene. It is the new name of the project I started in 2014, building upon my earlier work on Linux kernel and userspace hardening.
I co-founder Copperhead to have a sponsor for my open source work. It never owned my projects.
1
I still own 50% of Copperhead. I'm the co-owner of the company, with half of the voting shares. It's my company as much as it is James Donaldson's company. Unfortunately my rights as a shareholder have been disregarded along with the commitments made by the company. It's sad.
1
Them adding fraudulent copyright notices to the code, stripping my name off my blog posts and legacy documentation, etc. doesn't change that I own it and created it.
It's amusing that they leave up my legacy documentation with near zero relevance to their closed source product.
1
All part of pretending that they developed it when they didn't, pretending that it is the original project when it isn't and pretending that it a privacy / security hardened OS when it simply isn't what they do. AOSP is more private & secure than a poorly maintained branded fork.