System Hardening in Android 11
security.googleblog.com
System Hardening in Android 11
1–10 of 211 posts
Re: System Hardening in Android 11
#2> we did all that work on the OS but kept the GoogleService thing that is a sytemapp+kernelmodule+backdoor on top so we can continue to serve our users as they want, with more relevant ads.
Re: System Hardening in Android 11
#3> we did all that work on the OS but kept the GoogleService thing that is a sytemapp+kernelmodule+backdoor on top so we can continue to serve our users as they want, with more relevant ads.
But this work will still benefit Android derivatives that do not use Google services.
Re: System Hardening in Android 11
#4"In Android 11, Scudo [1] replaces jemalloc as the default native allocator for Android. Scudo is a hardened memory allocator designed to help detect and mitigate memory corruption bugs in the heap"
I am curious about the performance impact of this change.
Re: System Hardening in Android 11
#5> In Android 11, Scudo replaces jemalloc as the default native allocator for Android. Scudo is a hardened memory allocator designed to help detect and mitigate memory corruption bugs in the heap
This comment of mine did not age well: https://news.ycombinator.com/item?id=23560040. I'm curious what the performance impact of the change was?
Re: System Hardening in Android 11
#6> we did all that work on the OS but kept the GoogleService thing that is a sytemapp+kernelmodule+backdoor on top so we can continue to serve our users as they want, with more relevant ads.
Can we stop this 4chan style sarcastic comment with zero insight, please? I really don't want to see HN turn into 4chan or reddit or whatever.
Re: System Hardening in Android 11
#7> In Android 11, Scudo replaces jemalloc as the default native allocator for Android. Scudo is a hardened memory allocator designed to help detect and mitigate memory corruption bugs in the heap This comment of mine did not age well: https://news.ycombinator.com/item?id=23560040 . I'm curious what the performance impact of the change was?
I think it aged fine. I certainly hadn't heard of it, and I bet most people were in the same boat.
Really, you just asked a legitimate question, and now today you have a legitimate answer. I'd call that a win!
Re: System Hardening in Android 11
#8"In Android 11, Scudo [1] replaces jemalloc as the default native allocator for Android. Scudo is a hardened memory allocator designed to help detect and mitigate memory corruption bugs in the heap" I am curious about the performance impact of this change. [1] https://source.android.com/devices/tech/debug/scudo
I found this [0] 2019 blog post from what looks to be one of the people credited in the blog post (Kostya). It's not directly comparing Android+jemalloc vs Android+Scudo, but it does compare the two allocators and others.
[0] http://expertmiami.blogspot.com/2019/05/what-is-scudo-harden...
Re: System Hardening in Android 11
#9"In Android 11, Scudo [1] replaces jemalloc as the default native allocator for Android. Scudo is a hardened memory allocator designed to help detect and mitigate memory corruption bugs in the heap" I am curious about the performance impact of this change. [1] https://source.android.com/devices/tech/debug/scudo
Most Android apps probably allocate more with the JVM than they do malloc, right? My intuitive guess is that they could regress the performance of libc malloc and many people wouldn't notice.
Re: System Hardening in Android 11
#10> In Android 11, Scudo replaces jemalloc as the default native allocator for Android. Scudo is a hardened memory allocator designed to help detect and mitigate memory corruption bugs in the heap This comment of mine did not age well: https://news.ycombinator.com/item?id=23560040 . I'm curious what the performance impact of the change was?
re: Performance, my reply here [0] to a similar question might be of interest.