User continuously prompted for sudo password during testing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
PlainBox (Toolkit) |
Won't Fix
|
Wishlist
|
Unassigned |
Bug Description
ubuntu@am3:~$ dpkg -l |grep checkbox
ii checkbox-ng 0.4~dev+
ii plainbox-
ii python3-checkbox-ng 0.4~dev+
ii python3-
ubuntu@am3:~$ dpkg -l |grep plainbox
ii plainbox-
ii plainbox-
ii plainbox-
ii plainbox-
ii python3-plainbox 0.6~dev+
This is being run on a new ARM64 board for dev/test purposes. I discovered that while running the various server tests, anything that requires root access is prompting me for a sudo password when the test runs.
So, rather than being asked for sudo at the beginning and never again, I'm being prompted on each root-access test case to input the sudo password.
Related branches
- Daniel Manrique (community): Approve
-
Diff: 25 lines (+5/-0)2 files modifieddebian/changelog (+4/-0)
debian/control (+1/-0)
Changed in plainbox: | |
status: | In Progress → Confirmed |
milestone: | none → future |
Changed in plainbox: | |
status: | Confirmed → Fix Released |
plainbox's design is like this: it invokes the sudo runner every time it's needed, this is unlike checkbox which had a privileged "daemon" that took care of this.
Without a significant design change, we can't really solve this on the plainbox side. We *are* considering such a change but it's still in the early planning stages.
As a workaround, I can suggest configuring sudoers so that your user can run commands without needing a password.
As an interesting note, if you were using pkexec (i.e. not remotely, over ssh), you could just install the plainbox- insecure- policy package to achieve a similar effect.
Since this is "by design", I'll set this bug as triaged/wishlist and move to the plainbox engine where this stuff resides.