Conversation

This Tweet was deleted by the Tweet author. Learn more

Once the resources are available to support it, yes. It also needs to be supported by github.com/anestisb/andro. Aside from that, improving the support for existing devices is important. They are using prebuilts for a lot of vendor instead of building from source right now.

4:23 PM · May 9, 2019Twitter Web Client

Replying to

and

So that prevents applying compiler hardening to these components. Nothing can be done directly to harden firmware within GrapheneOS, whether it's open or closed source, since the signatures are verified, but these other vendor components can and should be hardened.

Replying to

and

A lot is included in AOSP and just not being built from it right now. Other parts are open sourced as part of Qualcomm's published code. There are some libraries and services that aren't, but they're part of the Qualcomm SDK so there is still the opportunity to harden them.