[Touch-packages] [Bug 1829609] Re: files in sudoers.d no longer being read or honored
This bug appears to be related to KDEneon only. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hostname in Ubuntu. https://bugs.launchpad.net/bugs/1829609 Title: files in sudoers.d no longer being read or honored Status in hostname package in Ubuntu: New Bug description: Previously reported bug not ever assigned: https://bugs.launchpad.net/ubuntu/+s...e/+bug/1584549 Currently using KDEneon User Edition LTS 18.04 fully updated. No known entry format in /etc/sudoers.d/ appear to be read by sudoers any longer. All files under /etc/sudoers.d/ are permissions 0440 and root owned. visudo -c confirms the syntax passes the checks. Prior to last month, files in suoders.d were read and worked IF you used the FQDM and not the hostname (as should be allowed thus the prior bug report). Some update must have broken the usage. I have attempted the following formats in /etc/sudoers.d/apt; stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt- get,/usr/bin/apt,/usr/bin/add-apt-repository,/usr/bin/apt-add- repository stuart office = (root) NOPASSWD: /usr/bin/apt- get,/usr/bin/apt,/usr/bin/add-apt-repository,/usr/bin/apt-add- repository stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt-get stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt stuart office.smith.lan = (root) NOPASSWD: /usr/bin/add-apt-repository stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt-add-repository stuart ALL = (root) NOPASSWD: /usr/bin/apt-get,/usr/bin/apt,/usr/bin /add-apt-repository,/usr/bin/apt-add-repository ALL ALL= (root) NOPASSWD: /usr/bin/apt-get,/usr/bin/apt,/usr/bin/add- apt-repository,/usr/bin/apt-add-repository The first one above worked in 16.04. Prior to that (15.04) the second one worked. I have tried all of these and none are honored. apt-cache policy sudo sudo: Installed: 1.8.21p2-3ubuntu1 Candidate: 1.8.21p2-3ubuntu1 Version table: *** 1.8.21p2-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hostname/+bug/1829609/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829609] Re: files in sudoers.d no longer being read or honored
This appears to be KDEneon only. Please close. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hostname in Ubuntu. https://bugs.launchpad.net/bugs/1829609 Title: files in sudoers.d no longer being read or honored Status in hostname package in Ubuntu: New Bug description: Previously reported bug not ever assigned: https://bugs.launchpad.net/ubuntu/+s...e/+bug/1584549 Currently using KDEneon User Edition LTS 18.04 fully updated. No known entry format in /etc/sudoers.d/ appear to be read by sudoers any longer. All files under /etc/sudoers.d/ are permissions 0440 and root owned. visudo -c confirms the syntax passes the checks. Prior to last month, files in suoders.d were read and worked IF you used the FQDM and not the hostname (as should be allowed thus the prior bug report). Some update must have broken the usage. I have attempted the following formats in /etc/sudoers.d/apt; stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt- get,/usr/bin/apt,/usr/bin/add-apt-repository,/usr/bin/apt-add- repository stuart office = (root) NOPASSWD: /usr/bin/apt- get,/usr/bin/apt,/usr/bin/add-apt-repository,/usr/bin/apt-add- repository stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt-get stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt stuart office.smith.lan = (root) NOPASSWD: /usr/bin/add-apt-repository stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt-add-repository stuart ALL = (root) NOPASSWD: /usr/bin/apt-get,/usr/bin/apt,/usr/bin /add-apt-repository,/usr/bin/apt-add-repository ALL ALL= (root) NOPASSWD: /usr/bin/apt-get,/usr/bin/apt,/usr/bin/add- apt-repository,/usr/bin/apt-add-repository The first one above worked in 16.04. Prior to that (15.04) the second one worked. I have tried all of these and none are honored. apt-cache policy sudo sudo: Installed: 1.8.21p2-3ubuntu1 Candidate: 1.8.21p2-3ubuntu1 Version table: *** 1.8.21p2-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hostname/+bug/1829609/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829609] [NEW] files in sudoers.d no longer being read or honored
Public bug reported: Previously reported bug not ever assigned: https://bugs.launchpad.net/ubuntu/+s...e/+bug/1584549 Currently using KDEneon User Edition LTS 18.04 fully updated. No known entry format in /etc/sudoers.d/ appear to be read by sudoers any longer. All files under /etc/sudoers.d/ are permissions 0440 and root owned. visudo -c confirms the syntax passes the checks. Prior to last month, files in suoders.d were read and worked IF you used the FQDM and not the hostname (as should be allowed thus the prior bug report). Some update must have broken the usage. I have attempted the following formats in /etc/sudoers.d/apt; stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt- get,/usr/bin/apt,/usr/bin/add-apt-repository,/usr/bin/apt-add-repository stuart office = (root) NOPASSWD: /usr/bin/apt-get,/usr/bin/apt,/usr/bin /add-apt-repository,/usr/bin/apt-add-repository stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt-get stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt stuart office.smith.lan = (root) NOPASSWD: /usr/bin/add-apt-repository stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt-add-repository stuart ALL = (root) NOPASSWD: /usr/bin/apt-get,/usr/bin/apt,/usr/bin /add-apt-repository,/usr/bin/apt-add-repository ALL ALL= (root) NOPASSWD: /usr/bin/apt-get,/usr/bin/apt,/usr/bin/add- apt-repository,/usr/bin/apt-add-repository The first one above worked in 16.04. Prior to that (15.04) the second one worked. I have tried all of these and none are honored. apt-cache policy sudo sudo: Installed: 1.8.21p2-3ubuntu1 Candidate: 1.8.21p2-3ubuntu1 Version table: *** 1.8.21p2-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: hostname (Ubuntu) Importance: Undecided Status: New ** Tags: sudo sudoers -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hostname in Ubuntu. https://bugs.launchpad.net/bugs/1829609 Title: files in sudoers.d no longer being read or honored Status in hostname package in Ubuntu: New Bug description: Previously reported bug not ever assigned: https://bugs.launchpad.net/ubuntu/+s...e/+bug/1584549 Currently using KDEneon User Edition LTS 18.04 fully updated. No known entry format in /etc/sudoers.d/ appear to be read by sudoers any longer. All files under /etc/sudoers.d/ are permissions 0440 and root owned. visudo -c confirms the syntax passes the checks. Prior to last month, files in suoders.d were read and worked IF you used the FQDM and not the hostname (as should be allowed thus the prior bug report). Some update must have broken the usage. I have attempted the following formats in /etc/sudoers.d/apt; stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt- get,/usr/bin/apt,/usr/bin/add-apt-repository,/usr/bin/apt-add- repository stuart office = (root) NOPASSWD: /usr/bin/apt- get,/usr/bin/apt,/usr/bin/add-apt-repository,/usr/bin/apt-add- repository stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt-get stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt stuart office.smith.lan = (root) NOPASSWD: /usr/bin/add-apt-repository stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt-add-repository stuart ALL = (root) NOPASSWD: /usr/bin/apt-get,/usr/bin/apt,/usr/bin /add-apt-repository,/usr/bin/apt-add-repository ALL ALL= (root) NOPASSWD: /usr/bin/apt-get,/usr/bin/apt,/usr/bin/add- apt-repository,/usr/bin/apt-add-repository The first one above worked in 16.04. Prior to that (15.04) the second one worked. I have tried all of these and none are honored. apt-cache policy sudo sudo: Installed: 1.8.21p2-3ubuntu1 Candidate: 1.8.21p2-3ubuntu1 Version table: *** 1.8.21p2-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hostname/+bug/1829609/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1584549] Re: sudoers not honoring hostnames
Now using 18.04 KDEneon and last month sometime an update broke this functionality even further. The FQDN and indeed no other format works any longer. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hostname in Ubuntu. https://bugs.launchpad.net/bugs/1584549 Title: sudoers not honoring hostnames Status in hostname package in Ubuntu: Confirmed Bug description: New Kubuntu 16.04 install, adding features from previous 15.04 install. Added exact copy of /etc/sudoers.d/apt from 15.04 to 16.04 but it does not work as expected. File contents: myusername myhostname = NOPASSWD: /usr/bin/apt, /usr/bin/apt-get, /usr/bin/add-apt-repository results in 15.04 in user "myusername" being able to run apt, apt-get, and add-apt-repository from the CLI using sudo without a password prompt. However, same exact syntax in 16.04 results in password prompt. In the 16.04 install, changing "myhostname" to "ALL" resumes the no password behavior. Both installs have exact same /etc/hosts files, running on bare metal on the same system, and the "hostname" command results in the same reply with the correct hostname. I have compared the subject files several times and there are no differences. No errors editing any of the files using visudo. Permissions and syntax same on both systems. This leads me to conclude sudoers is not honoring the hostname in the sudoers file(s). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hostname/+bug/1584549/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1584549] Re: sudoers not honoring hostnames
New info: Using the FQDN instead of the shortened hostname version works. As before, in 15.04 shortened hostname works in sudoers.d/ files but in 16.04 it does not. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hostname in Ubuntu. https://bugs.launchpad.net/bugs/1584549 Title: sudoers not honoring hostnames Status in hostname package in Ubuntu: New Bug description: New Kubuntu 16.04 install, adding features from previous 15.04 install. Added exact copy of /etc/sudoers.d/apt from 15.04 to 16.04 but it does not work as expected. File contents: myusername myhostname = NOPASSWD: /usr/bin/apt, /usr/bin/apt-get, /usr/bin/add-apt-repository results in 15.04 in user "myusername" being able to run apt, apt-get, and add-apt-repository from the CLI using sudo without a password prompt. However, same exact syntax in 16.04 results in password prompt. In the 16.04 install, changing "myhostname" to "ALL" resumes the no password behavior. Both installs have exact same /etc/hosts files, running on bare metal on the same system, and the "hostname" command results in the same reply with the correct hostname. I have compared the subject files several times and there are no differences. No errors editing any of the files using visudo. Permissions and syntax same on both systems. This leads me to conclude sudoers is not honoring the hostname in the sudoers file(s). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hostname/+bug/1584549/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1584549] [NEW] sudoers not honoring hostnames
Public bug reported: New Kubuntu 16.04 install, adding features from previous 15.04 install. Added exact copy of /etc/sudoers.d/apt from 15.04 to 16.04 but it does not work as expected. File contents: myusername myhostname = NOPASSWD: /usr/bin/apt, /usr/bin/apt-get, /usr/bin/add-apt-repository results in 15.04 in user "myusername" being able to run apt, apt-get, and add-apt-repository from the CLI using sudo without a password prompt. However, same exact syntax in 16.04 results in password prompt. In the 16.04 install, changing "myhostname" to "ALL" resumes the no password behavior. Both installs have exact same /etc/hosts files, running on bare metal on the same system, and the "hostname" command results in the same reply with the correct hostname. I have compared the subject files several times and there are no differences. No errors editing any of the files using visudo. Permissions and syntax same on both systems. This leads me to conclude sudoers is not honoring the hostname in the sudoers file(s). ** Affects: hostname (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hostname in Ubuntu. https://bugs.launchpad.net/bugs/1584549 Title: sudoers not honoring hostnames Status in hostname package in Ubuntu: New Bug description: New Kubuntu 16.04 install, adding features from previous 15.04 install. Added exact copy of /etc/sudoers.d/apt from 15.04 to 16.04 but it does not work as expected. File contents: myusername myhostname = NOPASSWD: /usr/bin/apt, /usr/bin/apt-get, /usr/bin/add-apt-repository results in 15.04 in user "myusername" being able to run apt, apt-get, and add-apt-repository from the CLI using sudo without a password prompt. However, same exact syntax in 16.04 results in password prompt. In the 16.04 install, changing "myhostname" to "ALL" resumes the no password behavior. Both installs have exact same /etc/hosts files, running on bare metal on the same system, and the "hostname" command results in the same reply with the correct hostname. I have compared the subject files several times and there are no differences. No errors editing any of the files using visudo. Permissions and syntax same on both systems. This leads me to conclude sudoers is not honoring the hostname in the sudoers file(s). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hostname/+bug/1584549/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1440608] Re: /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels except the latest one
For what it's worth, it seems it might be HOW the script is being called. Testing the apt-auto-removal script here (Kubuntu 15.04) with kernels 3.19.0-29-generic, 3.19.0-30-generic, and 3.19.0-31-generic installed and after a reboot to load -31: 1) Noticed the call to autoremove 3.19.0-30-generic. 2) Read /etc/apt/apt.conf.d/01autoremovekernels and saw -29 and -31 listed as "NeverAutoRemove" 3) Manually removed 3.19.0-29-generic. 4) Ran "sudo /etc/kernel/postinst.d/apt-auto-removal" 5) Re-read /etc/apt/apt.conf.d/01autoremovekernels and saw only -31 listed as "NeverAutoRemove" 6) Ran "sudo /etc/kernel/postinst.d/apt-auto-removal 3.19.0-31-generic" 7) Re-read /etc/apt/apt.conf.d/01autoremovekernels and saw -30 and -31 listed as "NeverAutoRemove" So it worked when called properly in that case. I thought it possible that part of the problem is it's being called with the wrong kernel version. I re-installed -25 and -21 along with -30 and -31. This resulted in -25 and -31 in the never remove list. But again: When apt-auto-removal is re-run with -31, the never remove list changes to -30 and -31. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1440608 Title: /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels except the latest one Status in apt package in Ubuntu: Confirmed Bug description: After installing a 3rd kernel currently 3.19.0-12-generic, the /etc/apt/apt.conf.d/01autoremove-kernels file looks normal listing the 3.19.0-11-generic and 3.19.0-12-generic with 3.19.0-10-generic listed to be autoremoved. But once autoremove is completed the machine requests to be rebooted and at that time the /etc/apt/apt.conf.d /01autoremove-kernels file lists the 3.19.0-12-generic and 3.19.0-10-generic kernels. So upon rebooting the 3.19.0-11-generic is requested to be autoremoved leaving only one kernel the latest one 3.19.0-12-generic. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: apt 1.0.9.7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: MATE Date: Sun Apr 5 17:03:01 2015 InstallationDate: Installed on 2015-04-02 (3 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Beta amd64 (20150401) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1440608/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp