Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 12 Mar 2015 20:31:42 -0700
From: Nick Kralevich <>
Cc: "CERT(R) Coordination Center" <>
Subject: Re: Vendor adoption of PIE INFO#934476 oss-security

I wanted to provide a followup on this year-old thread.

With the release of Android 5.0, Android has removed support for
non-PIE binaries [1] [2]. Attempting to run a non-PIE binary will
generate an error on Android. In this way, we ensure that all binaries
take full advantage of Android's ASLR implementation.

This is just one of the many security enhancements added in Android
5.*, and one that I hope other Linux distributions will pick up.


-- Nick

On Sun, Feb 16, 2014 at 11:54 AM, Nick Kralevich <> wrote:
> On Android, third party applications have always been compiled with
> -fPIC, ever since the initial release of Android. As mentioned earlier
> in this thread, the performance impacts of PIC and PIE are similar.
> Starting in Android 4.1, all dynamically linked ARM [1] and x86 [2]
> executables are compiled with PIE. Compiling with PIE on MIPS was
> added in Android 4.3 [3]. Statically linked executables with PIE are
> not supported today [4], although I'd love to see it in the future.
> I have yet to hear any complaint, on x86 or ARM, about any real world
> performance impact of PIE on Android, even though the code has been
> live and in user's hands for almost 2 years.
> [1]
> [2]
> [3]
> [4]

Nick Kralevich | Android Security | | 650.214.4037

Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.