Restrict user to run specific sudo command











up vote
2
down vote

favorite












Here is a script:



#!/bin/bash

user='my_sudo_user'
sudo -lU $user


I was trying to limit my non_sudo_user to have the ability to run this script. Using visudo, I tried:



non_sudo_user ALL=(ALL) NOPASSWD: /bin/bash /full/path/script.sh
non_sudo_user ALL=(ALL) NOPASSWD: /usr/bin/sudo -lU
non_sudo_user ALL=(ALL) NOPASSWD: /usr/bin/sudo -lU * # unsafe


None of them work. I get this message:



Sorry, user non_sudo_user is not allowed to execute 'list' as my_sudo_user on host123.


But I provided -l in sudoer file.



What can I do? This is Ubuntu by the way.



EDIT:



I actually run this script:



for u in $(awk -F'[/:]' '{if($3>=1000&&$3!=65534) print $1}' /etc/passwd); do sudo -lU $u ; done


So I don't have a definite list of users ahead of time.










share|improve this question




























    up vote
    2
    down vote

    favorite












    Here is a script:



    #!/bin/bash

    user='my_sudo_user'
    sudo -lU $user


    I was trying to limit my non_sudo_user to have the ability to run this script. Using visudo, I tried:



    non_sudo_user ALL=(ALL) NOPASSWD: /bin/bash /full/path/script.sh
    non_sudo_user ALL=(ALL) NOPASSWD: /usr/bin/sudo -lU
    non_sudo_user ALL=(ALL) NOPASSWD: /usr/bin/sudo -lU * # unsafe


    None of them work. I get this message:



    Sorry, user non_sudo_user is not allowed to execute 'list' as my_sudo_user on host123.


    But I provided -l in sudoer file.



    What can I do? This is Ubuntu by the way.



    EDIT:



    I actually run this script:



    for u in $(awk -F'[/:]' '{if($3>=1000&&$3!=65534) print $1}' /etc/passwd); do sudo -lU $u ; done


    So I don't have a definite list of users ahead of time.










    share|improve this question


























      up vote
      2
      down vote

      favorite









      up vote
      2
      down vote

      favorite











      Here is a script:



      #!/bin/bash

      user='my_sudo_user'
      sudo -lU $user


      I was trying to limit my non_sudo_user to have the ability to run this script. Using visudo, I tried:



      non_sudo_user ALL=(ALL) NOPASSWD: /bin/bash /full/path/script.sh
      non_sudo_user ALL=(ALL) NOPASSWD: /usr/bin/sudo -lU
      non_sudo_user ALL=(ALL) NOPASSWD: /usr/bin/sudo -lU * # unsafe


      None of them work. I get this message:



      Sorry, user non_sudo_user is not allowed to execute 'list' as my_sudo_user on host123.


      But I provided -l in sudoer file.



      What can I do? This is Ubuntu by the way.



      EDIT:



      I actually run this script:



      for u in $(awk -F'[/:]' '{if($3>=1000&&$3!=65534) print $1}' /etc/passwd); do sudo -lU $u ; done


      So I don't have a definite list of users ahead of time.










      share|improve this question















      Here is a script:



      #!/bin/bash

      user='my_sudo_user'
      sudo -lU $user


      I was trying to limit my non_sudo_user to have the ability to run this script. Using visudo, I tried:



      non_sudo_user ALL=(ALL) NOPASSWD: /bin/bash /full/path/script.sh
      non_sudo_user ALL=(ALL) NOPASSWD: /usr/bin/sudo -lU
      non_sudo_user ALL=(ALL) NOPASSWD: /usr/bin/sudo -lU * # unsafe


      None of them work. I get this message:



      Sorry, user non_sudo_user is not allowed to execute 'list' as my_sudo_user on host123.


      But I provided -l in sudoer file.



      What can I do? This is Ubuntu by the way.



      EDIT:



      I actually run this script:



      for u in $(awk -F'[/:]' '{if($3>=1000&&$3!=65534) print $1}' /etc/passwd); do sudo -lU $u ; done


      So I don't have a definite list of users ahead of time.







      linux permissions sudo






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Apr 20 '17 at 18:05

























      asked Apr 20 '17 at 17:05









      CppLearner

      180110




      180110






















          2 Answers
          2






          active

          oldest

          votes

















          up vote
          0
          down vote













          EDIT:
          complete rewrite after OP provided more information.



          Specify the user in /etc/sudoers as having permission to execute /usr/sbin/sudo.



          This will allow them to execute the sudo command, but they will have no permissions to run any other commands.



          I just tested this on CentOS-7.3.1611 with a brand new user account:



          testusr ALL=(ALL) NOPASSWD: /usr/sbin/sudo



          I do not know if there are any security implications of specifying the sudo command itself in the list of allowed commands
          Please review and test before you rely on this in a production environment...it may be insecure.






          share|improve this answer























          • Thanks, but it still complain it doesn't have permission to execute 'list'.
            – CppLearner
            Apr 20 '17 at 17:35












          • Okay, so I guess I don't understand why you would use sudo to run a script that invokes sudo to list the users commands. Just tell the user to execute sudo -l for their own commands or sudo -lU someuser to list the commands someuser is allowed to run.
            – 0xSheepdog
            Apr 20 '17 at 17:44






          • 1




            I am trying to run a report as the non_sudo_user to test whether "my_sudo_user" has sudo privilege or not. The best reliable way is to run sudo -lU as far as I know. The reason the non_sudo_user can't have full privilege because it is meant for read-only.
            – CppLearner
            Apr 20 '17 at 18:04










          • thank you, the /usr/sbin/sudo will allow my non sudo user to have full sudo privilege. It's okay, I might have to work around with this for now, but I am hoping someone could come up with a solution, but I appreciate your help!
            – CppLearner
            Apr 20 '17 at 18:34










          • Hmm, did you test what happens if testuser runs: sudo sudo -s? I suspect that results in a root shell.
            – derobert
            Apr 20 '17 at 18:53




















          up vote
          0
          down vote













          I think you can only list the commands a different user can run if you can run arbitrary commands as (ALL) that user. So instead...



          In sudoers:



          non_sudo_user ALL=(ALL) NOPASSWD: /usr/bin/sudo -l


          And to list them, running as non_sudo_user:



          for target_user in user1 user2 user3... ; do
          sudo -u "$target_user" sudo -l
          done





          share|improve this answer























          • this works, but using -u I am stuck on users who aren't sudoer as I am asked for password. That's the expected behavior, but not quite what I am looking for. It was the reason i went with -lU (U goes with the list option).
            – CppLearner
            Apr 20 '17 at 18:27










          • @CppLearner I think (haven't tested) you could change the sudoer rule to allow ALL instead of non_sudo_user, if I'm understanding you correctly. Though you probably shouldn't... (Or maybe change my_sudo_user to ALL, not exactly sure what you're going for)
            – derobert
            Apr 20 '17 at 18:50












          • @CppLearner oh! I see you edited your question—I've updated the answer. This should do what you want.
            – derobert
            Apr 20 '17 at 18:58











          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',
          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%2f360248%2frestrict-user-to-run-specific-sudo-command%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          2 Answers
          2






          active

          oldest

          votes








          2 Answers
          2






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          0
          down vote













          EDIT:
          complete rewrite after OP provided more information.



          Specify the user in /etc/sudoers as having permission to execute /usr/sbin/sudo.



          This will allow them to execute the sudo command, but they will have no permissions to run any other commands.



          I just tested this on CentOS-7.3.1611 with a brand new user account:



          testusr ALL=(ALL) NOPASSWD: /usr/sbin/sudo



          I do not know if there are any security implications of specifying the sudo command itself in the list of allowed commands
          Please review and test before you rely on this in a production environment...it may be insecure.






          share|improve this answer























          • Thanks, but it still complain it doesn't have permission to execute 'list'.
            – CppLearner
            Apr 20 '17 at 17:35












          • Okay, so I guess I don't understand why you would use sudo to run a script that invokes sudo to list the users commands. Just tell the user to execute sudo -l for their own commands or sudo -lU someuser to list the commands someuser is allowed to run.
            – 0xSheepdog
            Apr 20 '17 at 17:44






          • 1




            I am trying to run a report as the non_sudo_user to test whether "my_sudo_user" has sudo privilege or not. The best reliable way is to run sudo -lU as far as I know. The reason the non_sudo_user can't have full privilege because it is meant for read-only.
            – CppLearner
            Apr 20 '17 at 18:04










          • thank you, the /usr/sbin/sudo will allow my non sudo user to have full sudo privilege. It's okay, I might have to work around with this for now, but I am hoping someone could come up with a solution, but I appreciate your help!
            – CppLearner
            Apr 20 '17 at 18:34










          • Hmm, did you test what happens if testuser runs: sudo sudo -s? I suspect that results in a root shell.
            – derobert
            Apr 20 '17 at 18:53

















          up vote
          0
          down vote













          EDIT:
          complete rewrite after OP provided more information.



          Specify the user in /etc/sudoers as having permission to execute /usr/sbin/sudo.



          This will allow them to execute the sudo command, but they will have no permissions to run any other commands.



          I just tested this on CentOS-7.3.1611 with a brand new user account:



          testusr ALL=(ALL) NOPASSWD: /usr/sbin/sudo



          I do not know if there are any security implications of specifying the sudo command itself in the list of allowed commands
          Please review and test before you rely on this in a production environment...it may be insecure.






          share|improve this answer























          • Thanks, but it still complain it doesn't have permission to execute 'list'.
            – CppLearner
            Apr 20 '17 at 17:35












          • Okay, so I guess I don't understand why you would use sudo to run a script that invokes sudo to list the users commands. Just tell the user to execute sudo -l for their own commands or sudo -lU someuser to list the commands someuser is allowed to run.
            – 0xSheepdog
            Apr 20 '17 at 17:44






          • 1




            I am trying to run a report as the non_sudo_user to test whether "my_sudo_user" has sudo privilege or not. The best reliable way is to run sudo -lU as far as I know. The reason the non_sudo_user can't have full privilege because it is meant for read-only.
            – CppLearner
            Apr 20 '17 at 18:04










          • thank you, the /usr/sbin/sudo will allow my non sudo user to have full sudo privilege. It's okay, I might have to work around with this for now, but I am hoping someone could come up with a solution, but I appreciate your help!
            – CppLearner
            Apr 20 '17 at 18:34










          • Hmm, did you test what happens if testuser runs: sudo sudo -s? I suspect that results in a root shell.
            – derobert
            Apr 20 '17 at 18:53















          up vote
          0
          down vote










          up vote
          0
          down vote









          EDIT:
          complete rewrite after OP provided more information.



          Specify the user in /etc/sudoers as having permission to execute /usr/sbin/sudo.



          This will allow them to execute the sudo command, but they will have no permissions to run any other commands.



          I just tested this on CentOS-7.3.1611 with a brand new user account:



          testusr ALL=(ALL) NOPASSWD: /usr/sbin/sudo



          I do not know if there are any security implications of specifying the sudo command itself in the list of allowed commands
          Please review and test before you rely on this in a production environment...it may be insecure.






          share|improve this answer














          EDIT:
          complete rewrite after OP provided more information.



          Specify the user in /etc/sudoers as having permission to execute /usr/sbin/sudo.



          This will allow them to execute the sudo command, but they will have no permissions to run any other commands.



          I just tested this on CentOS-7.3.1611 with a brand new user account:



          testusr ALL=(ALL) NOPASSWD: /usr/sbin/sudo



          I do not know if there are any security implications of specifying the sudo command itself in the list of allowed commands
          Please review and test before you rely on this in a production environment...it may be insecure.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Apr 20 '17 at 18:14

























          answered Apr 20 '17 at 17:32









          0xSheepdog

          1,1151521




          1,1151521












          • Thanks, but it still complain it doesn't have permission to execute 'list'.
            – CppLearner
            Apr 20 '17 at 17:35












          • Okay, so I guess I don't understand why you would use sudo to run a script that invokes sudo to list the users commands. Just tell the user to execute sudo -l for their own commands or sudo -lU someuser to list the commands someuser is allowed to run.
            – 0xSheepdog
            Apr 20 '17 at 17:44






          • 1




            I am trying to run a report as the non_sudo_user to test whether "my_sudo_user" has sudo privilege or not. The best reliable way is to run sudo -lU as far as I know. The reason the non_sudo_user can't have full privilege because it is meant for read-only.
            – CppLearner
            Apr 20 '17 at 18:04










          • thank you, the /usr/sbin/sudo will allow my non sudo user to have full sudo privilege. It's okay, I might have to work around with this for now, but I am hoping someone could come up with a solution, but I appreciate your help!
            – CppLearner
            Apr 20 '17 at 18:34










          • Hmm, did you test what happens if testuser runs: sudo sudo -s? I suspect that results in a root shell.
            – derobert
            Apr 20 '17 at 18:53




















          • Thanks, but it still complain it doesn't have permission to execute 'list'.
            – CppLearner
            Apr 20 '17 at 17:35












          • Okay, so I guess I don't understand why you would use sudo to run a script that invokes sudo to list the users commands. Just tell the user to execute sudo -l for their own commands or sudo -lU someuser to list the commands someuser is allowed to run.
            – 0xSheepdog
            Apr 20 '17 at 17:44






          • 1




            I am trying to run a report as the non_sudo_user to test whether "my_sudo_user" has sudo privilege or not. The best reliable way is to run sudo -lU as far as I know. The reason the non_sudo_user can't have full privilege because it is meant for read-only.
            – CppLearner
            Apr 20 '17 at 18:04










          • thank you, the /usr/sbin/sudo will allow my non sudo user to have full sudo privilege. It's okay, I might have to work around with this for now, but I am hoping someone could come up with a solution, but I appreciate your help!
            – CppLearner
            Apr 20 '17 at 18:34










          • Hmm, did you test what happens if testuser runs: sudo sudo -s? I suspect that results in a root shell.
            – derobert
            Apr 20 '17 at 18:53


















          Thanks, but it still complain it doesn't have permission to execute 'list'.
          – CppLearner
          Apr 20 '17 at 17:35






          Thanks, but it still complain it doesn't have permission to execute 'list'.
          – CppLearner
          Apr 20 '17 at 17:35














          Okay, so I guess I don't understand why you would use sudo to run a script that invokes sudo to list the users commands. Just tell the user to execute sudo -l for their own commands or sudo -lU someuser to list the commands someuser is allowed to run.
          – 0xSheepdog
          Apr 20 '17 at 17:44




          Okay, so I guess I don't understand why you would use sudo to run a script that invokes sudo to list the users commands. Just tell the user to execute sudo -l for their own commands or sudo -lU someuser to list the commands someuser is allowed to run.
          – 0xSheepdog
          Apr 20 '17 at 17:44




          1




          1




          I am trying to run a report as the non_sudo_user to test whether "my_sudo_user" has sudo privilege or not. The best reliable way is to run sudo -lU as far as I know. The reason the non_sudo_user can't have full privilege because it is meant for read-only.
          – CppLearner
          Apr 20 '17 at 18:04




          I am trying to run a report as the non_sudo_user to test whether "my_sudo_user" has sudo privilege or not. The best reliable way is to run sudo -lU as far as I know. The reason the non_sudo_user can't have full privilege because it is meant for read-only.
          – CppLearner
          Apr 20 '17 at 18:04












          thank you, the /usr/sbin/sudo will allow my non sudo user to have full sudo privilege. It's okay, I might have to work around with this for now, but I am hoping someone could come up with a solution, but I appreciate your help!
          – CppLearner
          Apr 20 '17 at 18:34




          thank you, the /usr/sbin/sudo will allow my non sudo user to have full sudo privilege. It's okay, I might have to work around with this for now, but I am hoping someone could come up with a solution, but I appreciate your help!
          – CppLearner
          Apr 20 '17 at 18:34












          Hmm, did you test what happens if testuser runs: sudo sudo -s? I suspect that results in a root shell.
          – derobert
          Apr 20 '17 at 18:53






          Hmm, did you test what happens if testuser runs: sudo sudo -s? I suspect that results in a root shell.
          – derobert
          Apr 20 '17 at 18:53














          up vote
          0
          down vote













          I think you can only list the commands a different user can run if you can run arbitrary commands as (ALL) that user. So instead...



          In sudoers:



          non_sudo_user ALL=(ALL) NOPASSWD: /usr/bin/sudo -l


          And to list them, running as non_sudo_user:



          for target_user in user1 user2 user3... ; do
          sudo -u "$target_user" sudo -l
          done





          share|improve this answer























          • this works, but using -u I am stuck on users who aren't sudoer as I am asked for password. That's the expected behavior, but not quite what I am looking for. It was the reason i went with -lU (U goes with the list option).
            – CppLearner
            Apr 20 '17 at 18:27










          • @CppLearner I think (haven't tested) you could change the sudoer rule to allow ALL instead of non_sudo_user, if I'm understanding you correctly. Though you probably shouldn't... (Or maybe change my_sudo_user to ALL, not exactly sure what you're going for)
            – derobert
            Apr 20 '17 at 18:50












          • @CppLearner oh! I see you edited your question—I've updated the answer. This should do what you want.
            – derobert
            Apr 20 '17 at 18:58















          up vote
          0
          down vote













          I think you can only list the commands a different user can run if you can run arbitrary commands as (ALL) that user. So instead...



          In sudoers:



          non_sudo_user ALL=(ALL) NOPASSWD: /usr/bin/sudo -l


          And to list them, running as non_sudo_user:



          for target_user in user1 user2 user3... ; do
          sudo -u "$target_user" sudo -l
          done





          share|improve this answer























          • this works, but using -u I am stuck on users who aren't sudoer as I am asked for password. That's the expected behavior, but not quite what I am looking for. It was the reason i went with -lU (U goes with the list option).
            – CppLearner
            Apr 20 '17 at 18:27










          • @CppLearner I think (haven't tested) you could change the sudoer rule to allow ALL instead of non_sudo_user, if I'm understanding you correctly. Though you probably shouldn't... (Or maybe change my_sudo_user to ALL, not exactly sure what you're going for)
            – derobert
            Apr 20 '17 at 18:50












          • @CppLearner oh! I see you edited your question—I've updated the answer. This should do what you want.
            – derobert
            Apr 20 '17 at 18:58













          up vote
          0
          down vote










          up vote
          0
          down vote









          I think you can only list the commands a different user can run if you can run arbitrary commands as (ALL) that user. So instead...



          In sudoers:



          non_sudo_user ALL=(ALL) NOPASSWD: /usr/bin/sudo -l


          And to list them, running as non_sudo_user:



          for target_user in user1 user2 user3... ; do
          sudo -u "$target_user" sudo -l
          done





          share|improve this answer














          I think you can only list the commands a different user can run if you can run arbitrary commands as (ALL) that user. So instead...



          In sudoers:



          non_sudo_user ALL=(ALL) NOPASSWD: /usr/bin/sudo -l


          And to list them, running as non_sudo_user:



          for target_user in user1 user2 user3... ; do
          sudo -u "$target_user" sudo -l
          done






          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Apr 20 '17 at 18:58

























          answered Apr 20 '17 at 17:52









          derobert

          71.3k8151210




          71.3k8151210












          • this works, but using -u I am stuck on users who aren't sudoer as I am asked for password. That's the expected behavior, but not quite what I am looking for. It was the reason i went with -lU (U goes with the list option).
            – CppLearner
            Apr 20 '17 at 18:27










          • @CppLearner I think (haven't tested) you could change the sudoer rule to allow ALL instead of non_sudo_user, if I'm understanding you correctly. Though you probably shouldn't... (Or maybe change my_sudo_user to ALL, not exactly sure what you're going for)
            – derobert
            Apr 20 '17 at 18:50












          • @CppLearner oh! I see you edited your question—I've updated the answer. This should do what you want.
            – derobert
            Apr 20 '17 at 18:58


















          • this works, but using -u I am stuck on users who aren't sudoer as I am asked for password. That's the expected behavior, but not quite what I am looking for. It was the reason i went with -lU (U goes with the list option).
            – CppLearner
            Apr 20 '17 at 18:27










          • @CppLearner I think (haven't tested) you could change the sudoer rule to allow ALL instead of non_sudo_user, if I'm understanding you correctly. Though you probably shouldn't... (Or maybe change my_sudo_user to ALL, not exactly sure what you're going for)
            – derobert
            Apr 20 '17 at 18:50












          • @CppLearner oh! I see you edited your question—I've updated the answer. This should do what you want.
            – derobert
            Apr 20 '17 at 18:58
















          this works, but using -u I am stuck on users who aren't sudoer as I am asked for password. That's the expected behavior, but not quite what I am looking for. It was the reason i went with -lU (U goes with the list option).
          – CppLearner
          Apr 20 '17 at 18:27




          this works, but using -u I am stuck on users who aren't sudoer as I am asked for password. That's the expected behavior, but not quite what I am looking for. It was the reason i went with -lU (U goes with the list option).
          – CppLearner
          Apr 20 '17 at 18:27












          @CppLearner I think (haven't tested) you could change the sudoer rule to allow ALL instead of non_sudo_user, if I'm understanding you correctly. Though you probably shouldn't... (Or maybe change my_sudo_user to ALL, not exactly sure what you're going for)
          – derobert
          Apr 20 '17 at 18:50






          @CppLearner I think (haven't tested) you could change the sudoer rule to allow ALL instead of non_sudo_user, if I'm understanding you correctly. Though you probably shouldn't... (Or maybe change my_sudo_user to ALL, not exactly sure what you're going for)
          – derobert
          Apr 20 '17 at 18:50














          @CppLearner oh! I see you edited your question—I've updated the answer. This should do what you want.
          – derobert
          Apr 20 '17 at 18:58




          @CppLearner oh! I see you edited your question—I've updated the answer. This should do what you want.
          – derobert
          Apr 20 '17 at 18:58


















          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%2f360248%2frestrict-user-to-run-specific-sudo-command%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

          Morgemoulin

          Scott Moir

          Souastre