Conversation

Nov 22, 2018

I'm working on properly integrating github.com/AndroidHardeni into Bionic. However, I won't be able to expand my hardening work on the Android Open Source Project into a broader set of projects again without having proper funding for the development work, hardware and server costs.

Show this thread

It won't have any other privacy and security improvements until further work is funded. I won't be fixing all of the upstream bugs uncovered by the hardened allocator myself so it will probably have a lot of issues for the time being. It will have a bare minimum set of changes.

GitHub - GrapheneOS/platform_manifest: Repo manifest for the GrapheneOS mobile privacy and security...

The manifest for this will be at github.com/AndroidHardeni. I haven't pushed the hardened malloc integration yet, but I started pushing the minimal set of changes for proper AOSP builds. For example, fixing ro.product.model is needed for the Auditor app to work among other things.

github.com

Repo manifest for the GrapheneOS mobile privacy and security hardening project. - GitHub - GrapheneOS/platform_manifest: Repo manifest for the GrapheneOS mobile privacy and security hardening project.

If there was funding for making production hardened AOSP builds, progress could be made on chipping away at upstream bugs uncovered by the hardened malloc implementation. There could also be official releases with automatic updates and proper CTS + VTS testing for each release.

I won't be expanding it into a broader project without the appropriate funding / resources though. The scope is limited to integrating the hardened malloc implementation into AOSP and setting up proper builds of that. It won't be very usable/useful without fixing uncovered bugs.

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

Simply doing all the debugging and release engineering necessary for production releases is a huge amount of work without even adding more privacy/security features and needs funding. It's too much work for one person unless it's their entire job, and I won't do it alone again.

@lrvick

Replying to

GitHub - hashbang/os: Open source security/privacy focused AOSP rom

I am working on an reproducible build/sign/release system for Pixel 3 devices: github.com/hashbang/os I plan on incorperating your work incrementally. Feel free to reach out if you want to collaborate at all, else just keep open sourcing stuff and I'll keep doing my thing :)

github.com

Open source security/privacy focused AOSP rom. Contribute to hashbang/os development by creating an account on GitHub.

9:36 PM · Nov 24, 2018Twitter Web Client

Replying to

@lrvick

Using those driver packages won't provide fully functional builds and will break verified boot and some other security features. Most of the components in the vendor image are open source too, so if you want to build what you can from source you need to assemble it yourself.

Replying to

and

They merged everything needed for reproducible builds upstream for Linux, Chromium and AOSP so it's straightforward. Making production builds of AOSP with all the security features intact is more involved but the work has been done for Pixels and other devices don't support it.

Replying to

and

Funding and collaboration is needed for implementing and maintaining substantial privacy and security improvements for AOSP. Release engineering is difficult because of the time investment required for testing and then debugging the issues that are uncovered by the features.

Show replies

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

@lrvick

Replying to