Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87iluryaza.fsf@oldenburg.str.redhat.com>
Date: Mon, 10 Jan 2022 14:30:17 +0100
From: Florian Weimer <fweimer@...hat.com>
To: Rich Felker <dalias@...c.org>
Cc: Nihal Jere <nihal@...aljere.xyz>,  musl@...ts.openwall.com
Subject: Re: Dynamic linker segfault

* Rich Felker:

> By my understanding, p_align implies an understanding by the creator
> of the program that the load segment may be "over-mapped" (extra file
> contents visible and possibly executable) up to that alignment
> boundary due to page granularity. This isn't really a correctness
> contract but a security/hardening contract for folks who consider
> anti-ROP measures a boundary that should be enforced.

Not sure if I follow.  Do you mean p_align is purely for documenting
layout decisions by the link editor?  I suspect that the necessary
overlap would be visible by other means, too.

Thanks,
Florian

Powered by blists - more mailing lists

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