Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
For some reason, sudo does not recognize my Active Directory groups. Winbind (wbinfo, getent, and the such) works as intended, even returning the group in question. I even tried using one of the users from that Active Directory group, which sudo recognized without problems.
Basically,
Code:
%2007 ALL=(ALL) ALL
does not work, but
Code:
nilecirb ALL=(ALL) ALL
does. What could cause something like this to occur?
Thanks in advance,
nilecirb
UPDATE: Trying the primary group listed in getent passwd works, but does not achieve my ideal implementation. Has anyone gotten it working with secondary groups?
Thanks for replying, archtoad6. As a matter of fact, it's running Kubuntu. It's definitely possible that sudo's the one causing all the problems, but how would I determine if that's the case? I just tested local secondary groups with sudo, and those work perfectly.
One of the reasons that I don't (at least yet) run Kubuntu is the use of sudo rather than a properly set up root acct. As a result, I am probably not the best one to advise you.
If it's a Q of getting root privileges for a CLI command, try:
Code:
sudo su
or, if possible:
Code:
sudo su -
If it's a Q of a script not working, then setting up a root password might fix the problem:
Code:
sudo passwd
If none of this helps, try the Ubuntu forum or web site.
If it's a Q of getting root privileges for a CLI command, try:
Code:
sudo su
or, if possible:
Code:
sudo su -
The problem seems to lie more with sudo authentication than whatever command sudo tried to run. sudo <foo> does not work at all, whether <foo> is "su -" or any other command. My suspicions lean toward the way the sudo in Ubuntu's apt repository is configured. Anyone else have any ideas about the matter or have successfully authenticated with secondary AD groups using Ubuntu's sudo?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.