Package: wtmpdb Version: 0.12.0-2 Severity: important X-Debbugs-Cc: [email protected]
Dear Maintainer, wtmpdb respects the system-wide umask when creating /var/lib/wtmpdb/wtmp.db. This is inappropriate when the system-wide umask is 077 or something similarly restrictive, as wtmp.db can no longer be read by others (e.g., GNU screen). The problem occurs if the system-wide umask is configured during installation (before wtmp.db is created) or if wtmp.db is removed at any point after the system-wide umask has been configured. One solution would be to create wtmp.db as part of the wtmpdb package postinst. From my testing, I think just touching an empty file with the proper permissions would suffice. Another solution would be for wtmpdb to explicitly set the mode of wtmp.db to 644 every time the database file is created. I'm not sure whether it should occur if wtmp.db is an existing empty file. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.9.8-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages wtmpdb depends on: ii libaudit1 1:3.1.2-4 ii libc6 2.38-14 ii libsystemd0 256.2-1 ii libwtmpdb0 0.12.0-2 Versions of packages wtmpdb recommends: ii libpam-wtmpdb 0.12.0-2 wtmpdb suggests no packages. -- no debconf information
