Conversation

Daniel Micay
@DanielMicay
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.
1
2
Daniel Micay
@DanielMicay
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.
1
2
Daniel Micay
@DanielMicay
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.
2
3
Lance R. Vick ( @lrvick@mastodon.social )
@lrvick
Replying to
@DanielMicay
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
GitHub - hashbang/os: Open source security/privacy focused AOSP rom
Open source security/privacy focused AOSP rom. Contribute to hashbang/os development by creating an account on GitHub.
1
1
Daniel Micay
@DanielMicay
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.
2
Daniel Micay
@DanielMicay
Replying to
@DanielMicay
and
@lrvick
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.
1
Daniel Micay
@DanielMicay
Replying to
@DanielMicay
and
@lrvick
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.
2
Lance R. Vick ( @lrvick@mastodon.social )
@lrvick
Replying to
@DanielMicay
I have enough funding for build servers and image hosting. Also have a few willing testers. As long as the scope is -only- pixel/p devices right now this is looking fairly maintainable. Adding in all your patches ofc will take more test devices and a test channel but feasible.
1
Daniel Micay
@DanielMicay
Replying to
@lrvick
You aren't running the CTS and investigating all the issues it uncovers though. Building AOSP with reproducible builds is easy. It already exists and builds fine as is. Testing each release is time consuming and there are issues to investigate before even implementing features.
2