From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B76FF3858D38; Sun, 26 Feb 2023 17:22:59 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B76FF3858D38 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1677432179; bh=dFKppygEkKYc93TrVwfprpvREzp7qkwQFUjPRH81yms=; h=From:To:Subject:Date:In-Reply-To:References:From; b=yx1WNXuCXGH5a7UonAunoDwu4YcvbeDpq4luP0IBIgMndMLF9IdhCA2Qn8kkbYuTn SWQ3etK0jrGpQtIBc49XHycnW7EzfNWSAAm2FFjk0ZctIafm2yBgxWZNUKdAKPEZcA U7L24E0lKh7h6sEJSNdM5Y+yLXPEnnbdYOUb49fM= From: "stsp at users dot sourceforge.net" To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/30127] [rfe]: enable ld audit at run-time Date: Sun, 26 Feb 2023 17:22:59 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: dynamic-link X-Bugzilla-Version: 2.38 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: stsp at users dot sourceforge.net X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30127 --- Comment #28 from Stas Sergeev --- (In reply to Jonathon Anderson from comment #27) > There *will* be auditors that will not function properly under these > restrictions. Where would they come from and how could they became loaded by this API? > At the very least there needs to be some kind of flag > presented to the auditor at la_version-time to let it know that it has be= en > loaded in this (very) degraded state, so the auditor has a chance to refu= se > to load. Hmm, not really sure there are flags in la_version(). But I can instead disallow loading of such auditor and return an error. > So, IIUC you have an solib plugin (i.e. you don't control the application) > where you want/need to customize (a) the location the solib is loaded (or > where what the solib loads is loaded?) with la_premap and (b) the paths t= hat > your plugin loads with la_objsearch. a - yes b - no > Solibs are "position-independent" and should work no matter where they are > loaded (unless you're doing *really* dangerous and non-portable tricks wi= th > function pointers). I need that to make the 64bit solib to cooperate with 32bit VM. The memory of that VM is mapped to 64bit space. I need to map the lib to that window, but it should be relocated as if it is in the first 4Gb. For that I need 2 extensions instead of just 1. They are in that patch-set. But I am going to split it into multiple patches for easier understanding by reviewers. As currently no one understands it, but this is simply because the patch is too big. > (b) gives me bad vibes, Same here, I am not planning b. --=20 You are receiving this mail because: You are on the CC list for the bug.=