Sudoers snapd.conf will be ignored
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd |
Fix Released
|
Medium
|
Maciej Borzecki |
Bug Description
There is a sudoers configuration file in an ubuntu 20.04 install of snapd:
root@locutus:
snapd: /etc/sudoers.
Which contains:
# Allow snap-provided applications to work with sudo
Defaults secure_path += /snap/bin
However I don't believe this file gets parsed. I tried to create my own similar file 01-xxxx.conf alongside it for entirely unrelated reasons assuming the file name was consistent and it didn't work. On closer inspection it looks like sudo ignores any included files containing a period.
I don't really use snap in my environment so don't know if there's any impact to the above, but thought I'd be a good citizen and report.
Changed in snapd: | |
status: | In Progress → Fix Committed |
Changed in snapd: | |
milestone: | none → 2.46 |
Changed in snapd: | |
status: | Fix Committed → Fix Released |
And on top of that, secure_path cannot be overwritten or appended to. We stopped shipping the file on Fedora and Arch. It should be dropped from the deb too.