Re: [systemd-devel] Securing bind with systemd methods (was: bind-mount of /run/systemd for chrooted bind9/named)
On Tue, 18 Jul 2023 at 10:42:49 +0200, Marc Haber wrote: > That would be /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 on my > system (only output of find /lib /usr/lib -name 'ld-lin*'), and adding > that to ExecPaths doesnt allow my Executable to run. So it must be > something else (possibly in addition). The interoperable interpreter hard-coded in the ELF header for x86_64 is /lib64/ld-linux-x86-64.so.2 (yes, even on Debian, which otherwise doesn't generally use lib64). On Debian systems, that happens to be a symlink to /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2, which resolves to /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 as a result of the /usr merge, but those paths are implementation details of Debian rather than being part of the ABI. In container/namespace contexts you'll likely need to allow access to this via all three paths. smcv
[systemd-devel] Random freeze at booting Fedora 38
Hi, After upgrading Fedora 37 Workstation (which was fine) to Fedora 38 WS, I see occasional (random) freezing when booting. The freeze occurs generally in the screen where to select the user, where nothing is possible, only long press on the power button to stop the computer. I join 2 screenshots from Logs with an error message. What's the meaning, and how to correct it. Thanks for your help (I amn't a technician, only a regular user) GL
Re: [systemd-devel] Securing bind with systemd methods (was: bind-mount of /run/systemd for chrooted bind9/named)
On Tue, Jul 18, 2023 at 01:10:16AM +0300, Mantas Mikulėnas wrote: > On Mon, Jul 17, 2023, 15:44 Marc Haber > wrote: > > # /lib is necessary here, or execve will fail without indication for > > # reason - that was a surprise and hard to debug because even strace > > # didnt hint me towards the real issue > > ExecPaths=/usr/sbin/named /usr/sbin/rndc /lib > > > > This one in particular is not a systemd issue: I never claimed it to be. > All dynamically linked > binaries are executed through /lib/ld-linux*.so as their "interpreter". > (`file` will show the exact path.) I wish that had a dedicated errno, > though. That would be /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 on my system (only output of find /lib /usr/lib -name 'ld-lin*'), and adding that to ExecPaths doesnt allow my Executable to run. So it must be something else (possibly in addition). Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
