suid executable not elevating permissions but `sudo` does elevate












1














I'm trying to write a program that will quickly shut down a laptop without prompting for a password or confirmation. The laptop is running Linux, specifically Manjaro.



To that end, I'm trying to make a setuid executable called downnow that executes shutdown with fixed arguments (and also spawns a shell).



// downnow.c
#include <stdlib.h>

int main() {
system("shutdown --no-wall --halt now");
return 0;
}


then I compiled downnow, moved it to /bin, changed its owner and gave it setuid and setgid permissions:



$ sudo chown root /bin/downnow 

$ sudo chgrp root /bin/downnow

$ sudo chmod u+s /bin/downnow

$ sudo chmod g+s /bin/downnow


However, when I attempt to execute downnow as an unprivileged user, it can't communicate with systemd.



$ downnow 
Failed to halt system via logind: Interactive authentication required.
Failed to talk to init daemon.


I get the same message before and after ch{own,grp,mod}ing.



stat reports the same permissions on /bin/downnow and /usr/bin/sudo.



$ stat /bin/downnow 
File: /bin/downnow
Size: XXXX Blocks: XX IO Block: XXXX regular file
Device: XXXXX/XXXXX Inode: XXXXXX Links: 1
Access: (6755/-rwsr-sr-x) Uid: ( 0/ root) Gid: ( 0/ root)

$ stat /usr/bin/sudo
File: /usr/bin/sudo
Size: XXXXXX Blocks: XXX IO Block: XXXX regular file
Device: XXXXX/XXXXX Inode: XXXXXXX Links: 1
Access: (4755/-rwsr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)


Why might downnow fail to elevate its privileges when sudo works perfectly?










share|improve this question



























    1














    I'm trying to write a program that will quickly shut down a laptop without prompting for a password or confirmation. The laptop is running Linux, specifically Manjaro.



    To that end, I'm trying to make a setuid executable called downnow that executes shutdown with fixed arguments (and also spawns a shell).



    // downnow.c
    #include <stdlib.h>

    int main() {
    system("shutdown --no-wall --halt now");
    return 0;
    }


    then I compiled downnow, moved it to /bin, changed its owner and gave it setuid and setgid permissions:



    $ sudo chown root /bin/downnow 

    $ sudo chgrp root /bin/downnow

    $ sudo chmod u+s /bin/downnow

    $ sudo chmod g+s /bin/downnow


    However, when I attempt to execute downnow as an unprivileged user, it can't communicate with systemd.



    $ downnow 
    Failed to halt system via logind: Interactive authentication required.
    Failed to talk to init daemon.


    I get the same message before and after ch{own,grp,mod}ing.



    stat reports the same permissions on /bin/downnow and /usr/bin/sudo.



    $ stat /bin/downnow 
    File: /bin/downnow
    Size: XXXX Blocks: XX IO Block: XXXX regular file
    Device: XXXXX/XXXXX Inode: XXXXXX Links: 1
    Access: (6755/-rwsr-sr-x) Uid: ( 0/ root) Gid: ( 0/ root)

    $ stat /usr/bin/sudo
    File: /usr/bin/sudo
    Size: XXXXXX Blocks: XXX IO Block: XXXX regular file
    Device: XXXXX/XXXXX Inode: XXXXXXX Links: 1
    Access: (4755/-rwsr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)


    Why might downnow fail to elevate its privileges when sudo works perfectly?










    share|improve this question

























      1












      1








      1







      I'm trying to write a program that will quickly shut down a laptop without prompting for a password or confirmation. The laptop is running Linux, specifically Manjaro.



      To that end, I'm trying to make a setuid executable called downnow that executes shutdown with fixed arguments (and also spawns a shell).



      // downnow.c
      #include <stdlib.h>

      int main() {
      system("shutdown --no-wall --halt now");
      return 0;
      }


      then I compiled downnow, moved it to /bin, changed its owner and gave it setuid and setgid permissions:



      $ sudo chown root /bin/downnow 

      $ sudo chgrp root /bin/downnow

      $ sudo chmod u+s /bin/downnow

      $ sudo chmod g+s /bin/downnow


      However, when I attempt to execute downnow as an unprivileged user, it can't communicate with systemd.



      $ downnow 
      Failed to halt system via logind: Interactive authentication required.
      Failed to talk to init daemon.


      I get the same message before and after ch{own,grp,mod}ing.



      stat reports the same permissions on /bin/downnow and /usr/bin/sudo.



      $ stat /bin/downnow 
      File: /bin/downnow
      Size: XXXX Blocks: XX IO Block: XXXX regular file
      Device: XXXXX/XXXXX Inode: XXXXXX Links: 1
      Access: (6755/-rwsr-sr-x) Uid: ( 0/ root) Gid: ( 0/ root)

      $ stat /usr/bin/sudo
      File: /usr/bin/sudo
      Size: XXXXXX Blocks: XXX IO Block: XXXX regular file
      Device: XXXXX/XXXXX Inode: XXXXXXX Links: 1
      Access: (4755/-rwsr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)


      Why might downnow fail to elevate its privileges when sudo works perfectly?










      share|improve this question













      I'm trying to write a program that will quickly shut down a laptop without prompting for a password or confirmation. The laptop is running Linux, specifically Manjaro.



      To that end, I'm trying to make a setuid executable called downnow that executes shutdown with fixed arguments (and also spawns a shell).



      // downnow.c
      #include <stdlib.h>

      int main() {
      system("shutdown --no-wall --halt now");
      return 0;
      }


      then I compiled downnow, moved it to /bin, changed its owner and gave it setuid and setgid permissions:



      $ sudo chown root /bin/downnow 

      $ sudo chgrp root /bin/downnow

      $ sudo chmod u+s /bin/downnow

      $ sudo chmod g+s /bin/downnow


      However, when I attempt to execute downnow as an unprivileged user, it can't communicate with systemd.



      $ downnow 
      Failed to halt system via logind: Interactive authentication required.
      Failed to talk to init daemon.


      I get the same message before and after ch{own,grp,mod}ing.



      stat reports the same permissions on /bin/downnow and /usr/bin/sudo.



      $ stat /bin/downnow 
      File: /bin/downnow
      Size: XXXX Blocks: XX IO Block: XXXX regular file
      Device: XXXXX/XXXXX Inode: XXXXXX Links: 1
      Access: (6755/-rwsr-sr-x) Uid: ( 0/ root) Gid: ( 0/ root)

      $ stat /usr/bin/sudo
      File: /usr/bin/sudo
      Size: XXXXXX Blocks: XXX IO Block: XXXX regular file
      Device: XXXXX/XXXXX Inode: XXXXXXX Links: 1
      Access: (4755/-rwsr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)


      Why might downnow fail to elevate its privileges when sudo works perfectly?







      setuid






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 29 mins ago









      Gregory NisbetGregory Nisbet

      1,3771020




      1,3771020






















          0






          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
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f493583%2fsuid-executable-not-elevating-permissions-but-sudo-does-elevate%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          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%2f493583%2fsuid-executable-not-elevating-permissions-but-sudo-does-elevate%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

          Entries order in /etc/network/interfaces

          新発田市

          Grub takes very long (several minutes) to open Menu (in Multi-Boot-System)