On 23 June 2017 at 14:02, Kees Cook wrote:
> On Fri, Jun 23, 2017 at 6:52 AM, Kees Cook wrote:
>> On Thu, Jun 22, 2017 at 11:57 PM, Ard Biesheuvel
>> wrote:
>>> Hi Kees,
>>>
>>> On 22 June 2017 at 18:06, Kees Cook wrote:
Now that explicitly executed loaders are loaded in the mmap region,
>
On Fri, Jun 23, 2017 at 6:52 AM, Kees Cook wrote:
> On Thu, Jun 22, 2017 at 11:57 PM, Ard Biesheuvel
> wrote:
>> Hi Kees,
>>
>> On 22 June 2017 at 18:06, Kees Cook wrote:
>>> Now that explicitly executed loaders are loaded in the mmap region,
>>> position PIE binaries lower in the address space
On Thu, Jun 22, 2017 at 11:57 PM, Ard Biesheuvel
wrote:
> Hi Kees,
>
> On 22 June 2017 at 18:06, Kees Cook wrote:
>> Now that explicitly executed loaders are loaded in the mmap region,
>> position PIE binaries lower in the address space to avoid possible
>> collisions with mmap or stack regions.
Hi Kees,
On 22 June 2017 at 18:06, Kees Cook wrote:
> Now that explicitly executed loaders are loaded in the mmap region,
> position PIE binaries lower in the address space to avoid possible
> collisions with mmap or stack regions. For 64-bit, align to 4GB to
> allow runtimes to use the entire 32
Now that explicitly executed loaders are loaded in the mmap region,
position PIE binaries lower in the address space to avoid possible
collisions with mmap or stack regions. For 64-bit, align to 4GB to
allow runtimes to use the entire 32-bit address space for 32-bit
pointers.
Signed-off-by: Kees C
