Your message dated Wed, 10 Mar 2021 15:54:16 +0100 with message-id <[email protected]> and subject line Re: Bug#980364: sudo: segfault when /var/lib/sudo/lectured not writable has caused the Debian Bug report #980364, regarding sudo: segfault when /var/lib/sudo/lectured not writable to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 980364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980364 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: sudo Version: 1.8.27-1+deb10u2 Severity: normal On a system with disk errors, which had therefore remounted its file systems read-only, I tried to sudo in order to do further diagnostics as root, but sudo crashed with a segfault. I think it should be possible (perhaps with a special option) to continue without writing this file, even if it means I'll be lectured again if I run sudo again soon. In a situation like this, it might be more important to get root access at all. Even if it won't do this, a segfault is certainly a bug. % sudo su We trust you have received the usual lecture from the local System Administrator. It usually boils down to these three things: #1) Respect the privacy of others. #2) Think before you type. #3) With great power comes great responsibility. [sudo] password for frank: sudo: unable to mkdir /var/lib/sudo/lectured: Input/output error Segmentation fault -- System Information: Debian Release: 10.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-0.bpo.2-amd64 (SMP w/24 CPU cores) Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1), LANGUAGE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages sudo depends on: ii libaudit1 1:2.8.4-3 ii libc6 2.28-10 ii libpam-modules 1.3.1-5 ii libpam0g 1.3.1-5 ii libselinux1 2.8-1+b1 ii lsb-base 10.2019051400 sudo recommends no packages. sudo suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---control: notfound 1.8.27-1+deb10u3 control: notfound 1.9.5p2-3 Hi, after a short glance at mkdir_parents.c (that Frank was referring to code in this file), I see no immediate problems that need to be discussed with upstream. I can confirm that sudo not being able to create or write to the "lectured" directory does not lead to a segmentation fault, at least not in 1.8.27-1+deb10u3 or in 1.9.5p2-3. Cheers, -Hilko
--- End Message ---
