Conversation

Daniel Micay
@DanielMicay
I'll be releasing updated documentation on building proper production releases of Chromium and the Android Open Source Project with all the security features intact. As part of twitter.com/DanielMicay/st, there will be a manifest for testing AOSP with the new hardened allocator.
Quote Tweet
Daniel Micay
@DanielMicay
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
Twitter Web Client
4
Retweets
12
Likes
Daniel Micay
@DanielMicay
Replying to
@DanielMicay
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.
1
1
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