Trying to understand the difference between “modernNeo ALL=(ALL:ALL) ALL” and “modernNeo ALL=(ALL)...












0














so in the sudoers file, you can have either of the following lines



modernNeo ALL=(ALL:ALL) ALL

modernNeo ALL=(ALL) ALL


I looked at the following answers on here to understand this




  • https://askubuntu.com/questions/334318/sudoers-file-enable-nopasswd-for-user-all-commands/340669#340669

  • https://askubuntu.com/questions/546219/what-is-the-difference-between-root-all-allall-all-and-root-all-all-all/546228#546228

  • This post on Ubuntu Forums

  • https://unix.stackexchange.com/a/201866


Question 1



If I understand correctly from those above answers, (ALL:ALL) means that you can run the command as any user and any group and that (ALL) means that you can run the command as any user but your group remains the same [it remains your own group] regardless of the user you become when you use sudo with ALL for the third entry?



Question 2



But with (ALL:ALL)




  • If you can run it as any group, how does sudo decide what group you run the command as if you dont specify it on the commandline using -g?

  • does it first try to run it as your own group and then go through a list of all the groups on your machine before finding the group that allows you to run the command?

  • Where does it get the list of groups from and what is the order of the groups on that list?

  • Or does it just revert to using root for user and/or group when your preference for what user and/or group you want to become isn't specified? If that is the case, why do (ALL:ALL) when you can do (root:root) ?


Question 3



Furthermore, in this Ubuntu Forums post, with regards to the following lines 



%admin ALL=(ALL) ALL



%sudo   ALL=(ALL:ALL) ALL


They say that




Users in the admin group may become root. Users in the sudo group can only use the sudo command.

For instance, they could not sudo su
(ALL:ALL) refers to (user:group) that sudo will use. It can be specified with -u and -g when you run sudo. If you don't specify anything it will run as root:root, which is the default. That's how most end up using it anyway.




That confuses me... they are stating that if you can take on any group when running a command, then you are unable to become root?






permissions sudo







share|improve this question







New contributor




modernNeo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

























    0














    so in the sudoers file, you can have either of the following lines



    modernNeo ALL=(ALL:ALL) ALL
    
modernNeo ALL=(ALL) ALL


    I looked at the following answers on here to understand this




    • https://askubuntu.com/questions/334318/sudoers-file-enable-nopasswd-for-user-all-commands/340669#340669

    • https://askubuntu.com/questions/546219/what-is-the-difference-between-root-all-allall-all-and-root-all-all-all/546228#546228

    • This post on Ubuntu Forums

    • https://unix.stackexchange.com/a/201866


    Question 1



    If I understand correctly from those above answers, (ALL:ALL) means that you can run the command as any user and any group and that (ALL) means that you can run the command as any user but your group remains the same [it remains your own group] regardless of the user you become when you use sudo with ALL for the third entry?



    Question 2



    But with (ALL:ALL)




    • If you can run it as any group, how does sudo decide what group you run the command as if you dont specify it on the commandline using -g?

    • does it first try to run it as your own group and then go through a list of all the groups on your machine before finding the group that allows you to run the command?

    • Where does it get the list of groups from and what is the order of the groups on that list?

    • Or does it just revert to using root for user and/or group when your preference for what user and/or group you want to become isn't specified? If that is the case, why do (ALL:ALL) when you can do (root:root) ?


    Question 3



    Furthermore, in this Ubuntu Forums post, with regards to the following lines 



    %admin ALL=(ALL) ALL
    

    
%sudo   ALL=(ALL:ALL) ALL


    They say that




    Users in the admin group may become root. Users in the sudo group can only use the sudo command.

    For instance, they could not sudo su
    (ALL:ALL) refers to (user:group) that sudo will use. It can be specified with -u and -g when you run sudo. If you don't specify anything it will run as root:root, which is the default. That's how most end up using it anyway.




    That confuses me... they are stating that if you can take on any group when running a command, then you are unable to become root?






    permissions sudo







    share|improve this question







    New contributor




    modernNeo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.























      0












      0








      0







      so in the sudoers file, you can have either of the following lines



      modernNeo ALL=(ALL:ALL) ALL
      
modernNeo ALL=(ALL) ALL


      I looked at the following answers on here to understand this




      • https://askubuntu.com/questions/334318/sudoers-file-enable-nopasswd-for-user-all-commands/340669#340669

      • https://askubuntu.com/questions/546219/what-is-the-difference-between-root-all-allall-all-and-root-all-all-all/546228#546228

      • This post on Ubuntu Forums

      • https://unix.stackexchange.com/a/201866


      Question 1



      If I understand correctly from those above answers, (ALL:ALL) means that you can run the command as any user and any group and that (ALL) means that you can run the command as any user but your group remains the same [it remains your own group] regardless of the user you become when you use sudo with ALL for the third entry?



      Question 2



      But with (ALL:ALL)




      • If you can run it as any group, how does sudo decide what group you run the command as if you dont specify it on the commandline using -g?

      • does it first try to run it as your own group and then go through a list of all the groups on your machine before finding the group that allows you to run the command?

      • Where does it get the list of groups from and what is the order of the groups on that list?

      • Or does it just revert to using root for user and/or group when your preference for what user and/or group you want to become isn't specified? If that is the case, why do (ALL:ALL) when you can do (root:root) ?


      Question 3



      Furthermore, in this Ubuntu Forums post, with regards to the following lines 



      %admin ALL=(ALL) ALL
      

      
%sudo   ALL=(ALL:ALL) ALL


      They say that




      Users in the admin group may become root. Users in the sudo group can only use the sudo command.

      For instance, they could not sudo su
      (ALL:ALL) refers to (user:group) that sudo will use. It can be specified with -u and -g when you run sudo. If you don't specify anything it will run as root:root, which is the default. That's how most end up using it anyway.




      That confuses me... they are stating that if you can take on any group when running a command, then you are unable to become root?






      permissions sudo







      share|improve this question







      New contributor




      modernNeo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      so in the sudoers file, you can have either of the following lines



      modernNeo ALL=(ALL:ALL) ALL
      
modernNeo ALL=(ALL) ALL


      I looked at the following answers on here to understand this




      • https://askubuntu.com/questions/334318/sudoers-file-enable-nopasswd-for-user-all-commands/340669#340669

      • https://askubuntu.com/questions/546219/what-is-the-difference-between-root-all-allall-all-and-root-all-all-all/546228#546228

      • This post on Ubuntu Forums

      • https://unix.stackexchange.com/a/201866


      Question 1



      If I understand correctly from those above answers, (ALL:ALL) means that you can run the command as any user and any group and that (ALL) means that you can run the command as any user but your group remains the same [it remains your own group] regardless of the user you become when you use sudo with ALL for the third entry?



      Question 2



      But with (ALL:ALL)




      • If you can run it as any group, how does sudo decide what group you run the command as if you dont specify it on the commandline using -g?

      • does it first try to run it as your own group and then go through a list of all the groups on your machine before finding the group that allows you to run the command?

      • Where does it get the list of groups from and what is the order of the groups on that list?

      • Or does it just revert to using root for user and/or group when your preference for what user and/or group you want to become isn't specified? If that is the case, why do (ALL:ALL) when you can do (root:root) ?


      Question 3



      Furthermore, in this Ubuntu Forums post, with regards to the following lines 



      %admin ALL=(ALL) ALL
      

      
%sudo   ALL=(ALL:ALL) ALL


      They say that




      Users in the admin group may become root. Users in the sudo group can only use the sudo command.

      For instance, they could not sudo su
      (ALL:ALL) refers to (user:group) that sudo will use. It can be specified with -u and -g when you run sudo. If you don't specify anything it will run as root:root, which is the default. That's how most end up using it anyway.




      That confuses me... they are stating that if you can take on any group when running a command, then you are unable to become root?






      permissions sudo




      permissions sudo






      share|improve this question







      New contributor




      modernNeo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question







      New contributor




      modernNeo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question






      New contributor




      modernNeo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked 11 mins ago









      modernNeo

      1




      1




      New contributor




      modernNeo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      modernNeo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      modernNeo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.



























          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "106"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });






          modernNeo is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f490835%2ftrying-to-understand-the-difference-between-modernneo-all-allall-all-and-m%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown






























          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          modernNeo is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          modernNeo is a new contributor. Be nice, and check out our Code of Conduct.













          modernNeo is a new contributor. Be nice, and check out our Code of Conduct.












          modernNeo is a new contributor. Be nice, and check out our Code of Conduct.
















          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid …



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid …



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f490835%2ftrying-to-understand-the-difference-between-modernneo-all-allall-all-and-m%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          -

          Popular posts from this blog

          Accessing regular linux commands in Huawei's Dopra Linux

          Image
          4 Backstory: I have a Huawei HG8245 router in my house and I want to change the default username/password. I've tried following this guide but the config file always gets reset. My ISP isn't helping either so I'm looking for other ways to accomplish this. The router has telnet access so this seems like a way to change the credentials. The first shell I gain access to looks like this: WAP> Pressing "?" gives me a list of available commands which I've pasted here, the two interesting ones are "su" and "shell". I can't seem to get su access, even after logging in as root (challenge password prompt, and then nothing happens), but shell gives me a proper linux shell. WAP>shell BusyBox v1.18.4 (2017-12-26 17:06:34 CST) built-in shell (ash) Enter 'hel...
          Read more

          Can't connect RFCOMM socket: Host is down

          Image
          up vote 3 down vote favorite I have bluez 5.4.3 and I am attempting to communicate with a ble device through minicom. These two deceives (my computer and a bluno nano) are alreadt paired and this has been my method so far. #bluetoothctl # pair xx:xx:xx:xx:xx:xx # exit Everything is working well so far then... #sudo rfcomm connect /dev/rfcomm0 xx:xx:xx:xx:xx:xx 1 & [1] 3665 Can't connect RFCOMM socket: Host is down Does anyone know how to resolve this issue? Any help would be very much appreciated. bluetooth bluez share | improve this question asked Feb 9 '17 at 18:46 Brandon Knape 46 2 ...
          Read more

          Kernel panic - not syncing: Fatal Exception in Interrupt

          Image
          0 Every day this error occured on my pc, kernel panic error on interrupt, what will be the problem? linux-mint share asked 6 mins ago Vinod Selvin Vinod Selvin 1 1 New contributor Vinod Selvin is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct. add a comment ...
          Read more