Conversation

The AndroidHardening project has been renamed to GrapheneOS to reflect significant progress towards it becoming a broader and more sustainable project: github.com/GrapheneOS. It will be expanding into a broader and more sustainable project with more developers on board soon.

Security and privacy focused mobile OS with Android app compatibility. We focus on developing substantial privacy and security improvements. - GrapheneOS

3

25

59

In addition to the focus on developing privacy and security improvements for the Android Open Source Project, it will include more standalone sub-projects hardened malloc implementation that are portable to other OSes. The Auditor app and attestation service are another example.

1

2

3

Standalone projects will be MIT licensed like the hardened malloc implementation: github.com/GrapheneOS/har. Attestation work will be made MIT licensed soon. Changes to existing projects will use the upstream licenses, which is already the case for the Android changes (Apache 2).

hardened_malloc/LICENSE at main · GrapheneOS/hardened_malloc

Hardened allocator designed for modern systems. It has integration into Android's Bionic libc and can be used externally with musl and glibc as a dynamic library for use on other Linux-base...

1

1

3

It's being supported by some companies, but there will be a strong focus on preserving independence and distance from corporations, governments, etc. Lots of care will be taken to avoid dependence / coercion. There's already much more diverse sources of support and collaboration.

2

3

Once the project has expanded, it can gain official support for more devices, but it will be possible to easily build it for many devices due to Treble even without official support. Supporting QubesOS as a first-class target with proper integration is also still on the roadmap.

2

4

Replying to

This seems very interesting. You mention

integration. It means we should be than able to have the GrapheneOS as a TemplateVM in the QubesOS? 😎

2

Replying to

and

Yes, and over the long term proper integration to support the app functionality and all the frills like clipboard support. At the moment, I have working builds, but there are a lot of major blockers like needing the proper low-level update infrastructure and a decent boot chain.

9:48 PM · Mar 28, 2019Twitter Web Client

Replying to

and

Also, it's a real mess right now and isn't inside the normal source tree. To be even somewhat usable, it also needs work on input device setup along with configuring Android to use the desktop-oriented support rather than presenting a phone interface. Mesa is also very annoying.

1