Package: ltrace Version: 0.7.3-6.15 Severity: normal Dear Maintainer,
If program does a fork+exec of a sgid executable, then:
(a) ltrace -f program and strace -f program expectedly
don't let the child gain new provileges.
(b) strace program does, since it's not tracing the child
(c) ltrace program doesn't
This makes ltrace borderline useless for debugging stuff like
crontab(1).
Best,
наб
-- System Information:
Debian Release: 12.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-9-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND,
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages ltrace depends on:
ii libc6 2.36-9+deb12u1
ii libelf1 0.188-2.1
ii libselinux1 3.4-1+b6
ltrace recommends no packages.
ltrace suggests no packages.
-- no debconf information
signature.asc
Description: PGP signature
