Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
From: Florian Weimer <hidden>
Date: 2024-07-08 16:26:33
Also in:
linux-fsdevel, linux-integrity, linux-security-module, lkml
Possibly related (same subject, not in this thread)
- 2024-08-09 · Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2) · Jeff Xu <hidden>
- 2024-08-09 · Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2) · Mickaël Salaün <mic@digikod.net>
- 2024-08-05 · Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2) · Jeff Xu <hidden>
- 2024-07-23 · Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2) · Mickaël Salaün <mic@digikod.net>
- 2024-07-23 · Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2) · Mickaël Salaün <mic@digikod.net>
* Jeff Xu:
Will dynamic linkers use the execveat(AT_CHECK) to check shared libraries too ? or just the main executable itself.
I expect that dynamic linkers will have to do this for everything they map. Usually, that does not include the maim program, but this can happen with explicit loader invocations (“ld.so /bin/true”). Thanks, Florian