← Back to context

Comment by randomblock1

20 hours ago

This is trivial to fix, at least for you.

  %corestaff ALL=NOPASSWD: /usr/bin/mailq "", \
                           /usr/sbin/exim -bp, \
                           /usr/sbin/exim -bpa, \
                           /usr/sbin/exim -bpc, \
                           /usr/sbin/exim -bpr, \
                           /usr/sbin/exim -bpu

That being said there definitely should be an automated way to check for incompatibilities between normal and rust sudo.

13 comments

randomblock1

Reply
throw0101c  4 hours ago

> This is trivial to fix, at least for you.

Or one could just install (real) sudo instead of (fake) sudo.

Installing real sudo is something I will have to do when (if) we move to 26.04 because we need LDAP functionality, and fake sudo does not provide that.

dangistan202611  19 hours ago

Before you know it, you will be needing a workaround for every replacement tool you use in Ubuntu. This is what makes it unacceptable.

foxhill  20 hours ago

forgive me if i’m wrong. i don’t think you’ve ever had to administer more than a handful of machines. your “fix” is irrelevant.

> That being said there definitely should be an automated way to check for incompatibilities between normal and rust sudo.

yes. it’s called the bare minimum.

  • 9dev  20 hours ago

    I do manage more than a handful of machines, and that means using automation tools and IaC as much as possible, while avoiding humans using shells as much as possible. I’m struggling to enumerate a lot of use cases for a bespoke sudo configuration that shouldn’t be a proper setup.