sudo not properly cleaning out timestamp directory
Bug #1458031 reported by
Marc Deslauriers
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
sudo (Debian) |
Fix Released
|
Unknown
|
|||
sudo (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Wily |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Sudo 1.8.10 switched to a new time stamp file format that uses the monotonic clock. Timestamp files moved from /var/lib/sudo to /var/lib/sudo/ts.
At boot, the contents of the /var/lib/sudo/ts directory needs to be deleted, as per the warning in the build log:
configure: Warning: the /var/lib/sudo/ts directory must be cleared at boot time.
configure: You may need to create a startup item to do this.
The sudo package ships with both an init script and a systemd unit file. Unfortunately, the init script sets the date on the timestamp files to epoch, which is no longer the proper way to invalidate them. The systemd unit file doesn't seem to work at all.
Related branches
Changed in sudo (Ubuntu Wily): | |
status: | New → Confirmed |
Changed in sudo (Debian): | |
status: | Unknown → New |
Changed in sudo (Debian): | |
status: | New → Fix Released |
To post a comment you must log in.
This bug was fixed in the package sudo - 1.8.12-1ubuntu2
---------------
sudo (1.8.12-1ubuntu2) wily; urgency=medium
* Use tmpfs location to store timestamp files (LP: #1458031) sudo.service, debian/ sudo.sudo. init: stop t-helper.
- debian/rules: change --with-rundir to /var/run/sudo
- debian/rules, debian/
shipping init script and service file, as they are no longer
necessary.
- debian/*.preinst, debian/*.postinst, debian/*.postrm: remove old init
script with dpkg-maintscrip
- debian/*.postinst: remove old /var/run/sudo to /var/lib/sudo
transition code, remove old /var/lib/sudo/ts timestamp directory.
-- Marc Deslauriers <email address hidden> Fri, 05 Jun 2015 09:31:38 -0400