GrapheneOS

Look at the underhanded way they attempted to get him in trouble with his university and endanger his work on obtaining a doctorate. Meanwhile, they depend on the work of developers like this so they can leech off it and sell and expensive product funding their attacks on them.

https://renlord.com/posts/2020-03-25-copperheados-legal-threat/ … is an earlier example of them threatening a developer (a student) for porting code published by our lead developer in 2015 under the Apache 2 license. We never had any copyright assignment and the work was not done for Copperhead or attributed to them.

They're dependent on the past and present work of the open source project they're so desperate to harm and destroy. They fraudulently claim ownership and credit for our work. They're building a business based on masquerading as the open source project they're trying to wipe out.

They're ripping off customers with expensive products putting them at risk rather than protecting them. They're in the business of marketing and branding, not privacy and security. They mislead with fraudulent claims and their response to criticism is misdirection and more lies.

Copperhead sells an expensive, closed source OS product almost entirely based on forking our past work. The main thing they've done is adding dangerous tracking to the update system to enforce licensing. It seriously lags behind security and OS updates and is not truly hardened.

Copperhead filed a baseless lawsuit against our lead developer based on false claims. We've filed counterclaims against them and we're filing our own lawsuit against them based on their fraud. Can read our initial legal response here: https://grapheneos.org/legal/Micay_%20Copperhead_%20Statement%20of%20Defendant%20and%20Counterclaim.pdf … Spread the word.

In the meantime, you can manually add the battery optimization exemption via Settings ➔ Apps & notifications ➔ Special app access ➔ Battery optimization where you can select "All apps", scroll down to the Clock app and manually add an exemption. Should get this added upstream.

We're working on a new release fixing another upstream issue with the Clock app from the Android Open Source Project. Our last release fixed many issues with it but introduced some new problems due to moving to a newer target API level. It needs a battery optimization exemption.

Pixel 2 and 2 XL may get the full November/December security updates in December. There were already firmware security fixes and improvements this month for newer generation devices including GPU firmware with better IOMMU isolation. Our recommendation is moving to a Pixel 4a.

Pixel 2 and 2 XL are nearing end-of-life and we're be switching to supporting them via separate extended support releases. They've been marked as obsolete instead of legacy devices. Lack of firmware updates this month means they'll be stuck at the 2020-11-01 security patch level.

Despite now sending the attestation root with the other certificates in the response, the QR codes will be less dense thanks to an improved static DEFLATE dictionary. It'd still be nice if the new official root was ECDSA rather than RSA or if there were separate roots for each.

Auditor now has support for the Pixel 4a with either the stock OS or GrapheneOS. It also supports the new key attestation root which may be required for new batches of existing devices. This required changing AttestationServer database and a new version of the Auditor protocol.

Our mail server has used DANE from the beginning. Unlike browsers, there's broad support for it among mail servers. Gmail doesn't support it for political reasons. MTA-STS only provides an equivalent to HSTS without preloading. It relies on DNS security regardless, as do CAs.