Conversation

Months ago my phone died and now I need 1+ man-week to de-backdoor my new Pixel 4. Being mostly phoneless warms me up to a simple device that respects my rights out of the box. Continuing phone detox until I get a Pinephone or Librem 5. I'm done funding #SurveillanceCapitalism twitter.com/ashk4n/status/

This Tweet is unavailable.

This Tweet is from a suspended account. Learn more

Replying to

and

Neither of the devices is open hardware and neither has open firmware, despite misconceptions created by misleading marketing. The Librem 5 is deliberately locked down to prevent updating the firmware. Neither is close to the security requirements for official GrapheneOS support.

6:02 AM · Apr 15, 2020Twitter Web App

Retweets

Likes

Lance R. Vick ( @lrvick@mastodon.social )

Replying to

and

The secure boot story leaves a lot to be desired on both devices to be sure but it will be possible to run with dramatically fewer blobs and your choice of several operating systems which might be less work to harden than reversing all android blobs. Tough tradeoffs to be sure.

Lance R. Vick ( @lrvick@mastodon.social )

Replying to

I may net circle back to AOSP if I get the time to finish the pixel 4 port but that is always the problem. The incredible amount of time it takes to try and make Android tolerable. It is a full time job and every project cuts different security corners to ship.

Replying to

See grapheneos.org/faq#device-sup for an overview of device support including the requirements for official support. We can't provide official support for insecure devices with vulnerabilities that can't be patched. Similarly, the hardware needs to provide the standard hardware-based

Replying to

security features including the hardware-backed keystores used by the OS and apps, support for real verified boot and attestation, modern mitigations, proper IOMMU integration / setup for the components, hardware key derivation support, Wi-Fi anonymity beyond just MAC rand, etc.

Show replies