sudoer not allowing only ALL as commands to user on some systems











up vote
0
down vote

favorite












I am seeing a strange behavior related to sudo on a specific set of systems but not on others.
I am not sure If there is some specific configuration change required here, which is missing.



The sudoer configuration is to enable non root users (I have used testuser in below example)
to install and setup the product packages. The Operating system is SUSE 12.



Following is the behavior seen on problematic scenario:



1.) Initially when sudoers is not configured we get something like this:



# sudo -l -U testuser
User testuser is not allowed to run sudo on <node>.


2.) Next if we create the /etc/sudoers.d/prodtest_install file:



Cmnd_Alias PROD_NODEKITS = /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install org_prod_test.rpm, 
/usr/bin/zypper --non-interactive --repo local --no-gpg-checks install org_prod_pkg1.rpm,
/usr/bin/zypper --non-interactive --repo local --no-gpg-checks install org_prod_pkg2.rpm,
/usr/bin/zypper --non-interactive --repo local --no-gpg-checks install pkg3.rpm
Cmnd_Alias PROD_NODESETUP = /opt/org/prod/test/bin/prod-setup
testuser ALL=(root) NOPASSWD: PROD_NODEKITS
testuser ALL=(root) NOPASSWD: PROD_NODESETUP
Defaults!PROD_NODEKITS !requiretty
Defaults!PROD_NODESETUP !requiretty


Still we see something like:



# sudo -l -U testuser
User testuser is not allowed to run sudo on <node>.


testuser is also not able to use any of the above commands:
ie. say:



# sudo /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install pkg3.rpm


will not work and asks for user passwords and even if we enter passwords the command does not go through.



3.) But, if we add 2 extra lines "testuser ALL=(root) NOPASSWD: ALL" and "testuser ALL=(ALL) ALL" to allow all commands in /etc/sudoers.d/prodtest_install:



Cmnd_Alias PROD_NODEKITS = /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install org_prod_test.rpm, 
/usr/bin/zypper --non-interactive --repo local --no-gpg-checks install org_prod_pkg1.rpm,
/usr/bin/zypper --non-interactive --repo local --no-gpg-checks install org_prod_pkg2.rpm,
/usr/bin/zypper --non-interactive --repo local --no-gpg-checks install pkg3.rpm
Cmnd_Alias PROD_NODESETUP = /opt/org/prod/test/bin/prod-setup
testuser ALL=(root) NOPASSWD: PROD_NODEKITS
testuser ALL=(root) NOPASSWD: ALL
testuser ALL=(ALL) ALL
testuser ALL=(root) NOPASSWD: PROD_NODESETUP
Defaults!PROD_NODEKITS !requiretty
Defaults!PROD_NODESETUP !requiretty


Then we see something like this:



# sudo -l -U testuser
Matching Defaults entries for testuser on <node>:
always_set_home, secure_path=/usr/sbin:/usr/bin:/sbin:/bin, env_reset, env_keep="LANG LC_ADDRESS LC_CTYPE LC_COLLATE LC_IDENTIFICATION
LC_MEASUREMENT LC_MESSAGES LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONE LC_TIME LC_ALL LANGUAGE LINGUAS XDG_SESSION_COOKIE",
!insults

Runas and Command-specific defaults for testuser:
Defaults!/opt/org/prod/test/bin/prod !requiretty
Defaults!/usr/bin/zypper --non-interactive --repo local --no-gpg-checks install org_prod_test.rpm, /usr/bin/zypper --non-interactive
--repo local --no-gpg-checks install org_prod_pkg1.rpm, /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install
org_prod_pkg2.rpm, /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install pkg3.rpm !requiretty
Defaults!/opt/org/prod/test/bin/prod-setup !requiretty

User testuser may run the following commands on <node>:
(root) NOPASSWD: ALL
(ALL) ALL


I am not sure why specific commands are not getting listed as well as not working with sudo.
This system is also not having /etc/sudo.conf which might elimates a different sudo plugin being used.



However, If I do add the /etc/sudoers.d/prodtest_install as provided above on other local SUSE 12 test systems
there is no issue and I see the following extra lines listed on doing "sudo -l -U testuser":



User testuser may run the following commands on <local_node>:
(root) NOPASSWD: /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install org_prod_test.rpm, /usr/bin/zypper
--non-interactive --repo local --no-gpg-checks install org_prod_pkg1.rpm, /usr/bin/zypper --non-interactive --repo local --no-gpg-checks
install org_prod_pkg2.rpm, /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install pkg3.rpm
(root) NOPASSWD: /opt/org/prod/test/bin/prod-setup


Is there anything that needs to be configured differently on the problematic system/ shoudl I check for something?



Thanks and warm regards,
Prasad










share|improve this question







New contributor




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
























    up vote
    0
    down vote

    favorite












    I am seeing a strange behavior related to sudo on a specific set of systems but not on others.
    I am not sure If there is some specific configuration change required here, which is missing.



    The sudoer configuration is to enable non root users (I have used testuser in below example)
    to install and setup the product packages. The Operating system is SUSE 12.



    Following is the behavior seen on problematic scenario:



    1.) Initially when sudoers is not configured we get something like this:



    # sudo -l -U testuser
    User testuser is not allowed to run sudo on <node>.


    2.) Next if we create the /etc/sudoers.d/prodtest_install file:



    Cmnd_Alias PROD_NODEKITS = /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install org_prod_test.rpm, 
    /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install org_prod_pkg1.rpm,
    /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install org_prod_pkg2.rpm,
    /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install pkg3.rpm
    Cmnd_Alias PROD_NODESETUP = /opt/org/prod/test/bin/prod-setup
    testuser ALL=(root) NOPASSWD: PROD_NODEKITS
    testuser ALL=(root) NOPASSWD: PROD_NODESETUP
    Defaults!PROD_NODEKITS !requiretty
    Defaults!PROD_NODESETUP !requiretty


    Still we see something like:



    # sudo -l -U testuser
    User testuser is not allowed to run sudo on <node>.


    testuser is also not able to use any of the above commands:
    ie. say:



    # sudo /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install pkg3.rpm


    will not work and asks for user passwords and even if we enter passwords the command does not go through.



    3.) But, if we add 2 extra lines "testuser ALL=(root) NOPASSWD: ALL" and "testuser ALL=(ALL) ALL" to allow all commands in /etc/sudoers.d/prodtest_install:



    Cmnd_Alias PROD_NODEKITS = /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install org_prod_test.rpm, 
    /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install org_prod_pkg1.rpm,
    /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install org_prod_pkg2.rpm,
    /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install pkg3.rpm
    Cmnd_Alias PROD_NODESETUP = /opt/org/prod/test/bin/prod-setup
    testuser ALL=(root) NOPASSWD: PROD_NODEKITS
    testuser ALL=(root) NOPASSWD: ALL
    testuser ALL=(ALL) ALL
    testuser ALL=(root) NOPASSWD: PROD_NODESETUP
    Defaults!PROD_NODEKITS !requiretty
    Defaults!PROD_NODESETUP !requiretty


    Then we see something like this:



    # sudo -l -U testuser
    Matching Defaults entries for testuser on <node>:
    always_set_home, secure_path=/usr/sbin:/usr/bin:/sbin:/bin, env_reset, env_keep="LANG LC_ADDRESS LC_CTYPE LC_COLLATE LC_IDENTIFICATION
    LC_MEASUREMENT LC_MESSAGES LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONE LC_TIME LC_ALL LANGUAGE LINGUAS XDG_SESSION_COOKIE",
    !insults

    Runas and Command-specific defaults for testuser:
    Defaults!/opt/org/prod/test/bin/prod !requiretty
    Defaults!/usr/bin/zypper --non-interactive --repo local --no-gpg-checks install org_prod_test.rpm, /usr/bin/zypper --non-interactive
    --repo local --no-gpg-checks install org_prod_pkg1.rpm, /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install
    org_prod_pkg2.rpm, /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install pkg3.rpm !requiretty
    Defaults!/opt/org/prod/test/bin/prod-setup !requiretty

    User testuser may run the following commands on <node>:
    (root) NOPASSWD: ALL
    (ALL) ALL


    I am not sure why specific commands are not getting listed as well as not working with sudo.
    This system is also not having /etc/sudo.conf which might elimates a different sudo plugin being used.



    However, If I do add the /etc/sudoers.d/prodtest_install as provided above on other local SUSE 12 test systems
    there is no issue and I see the following extra lines listed on doing "sudo -l -U testuser":



    User testuser may run the following commands on <local_node>:
    (root) NOPASSWD: /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install org_prod_test.rpm, /usr/bin/zypper
    --non-interactive --repo local --no-gpg-checks install org_prod_pkg1.rpm, /usr/bin/zypper --non-interactive --repo local --no-gpg-checks
    install org_prod_pkg2.rpm, /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install pkg3.rpm
    (root) NOPASSWD: /opt/org/prod/test/bin/prod-setup


    Is there anything that needs to be configured differently on the problematic system/ shoudl I check for something?



    Thanks and warm regards,
    Prasad










    share|improve this question







    New contributor




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






















      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I am seeing a strange behavior related to sudo on a specific set of systems but not on others.
      I am not sure If there is some specific configuration change required here, which is missing.



      The sudoer configuration is to enable non root users (I have used testuser in below example)
      to install and setup the product packages. The Operating system is SUSE 12.



      Following is the behavior seen on problematic scenario:



      1.) Initially when sudoers is not configured we get something like this:



      # sudo -l -U testuser
      User testuser is not allowed to run sudo on <node>.


      2.) Next if we create the /etc/sudoers.d/prodtest_install file:



      Cmnd_Alias PROD_NODEKITS = /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install org_prod_test.rpm, 
      /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install org_prod_pkg1.rpm,
      /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install org_prod_pkg2.rpm,
      /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install pkg3.rpm
      Cmnd_Alias PROD_NODESETUP = /opt/org/prod/test/bin/prod-setup
      testuser ALL=(root) NOPASSWD: PROD_NODEKITS
      testuser ALL=(root) NOPASSWD: PROD_NODESETUP
      Defaults!PROD_NODEKITS !requiretty
      Defaults!PROD_NODESETUP !requiretty


      Still we see something like:



      # sudo -l -U testuser
      User testuser is not allowed to run sudo on <node>.


      testuser is also not able to use any of the above commands:
      ie. say:



      # sudo /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install pkg3.rpm


      will not work and asks for user passwords and even if we enter passwords the command does not go through.



      3.) But, if we add 2 extra lines "testuser ALL=(root) NOPASSWD: ALL" and "testuser ALL=(ALL) ALL" to allow all commands in /etc/sudoers.d/prodtest_install:



      Cmnd_Alias PROD_NODEKITS = /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install org_prod_test.rpm, 
      /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install org_prod_pkg1.rpm,
      /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install org_prod_pkg2.rpm,
      /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install pkg3.rpm
      Cmnd_Alias PROD_NODESETUP = /opt/org/prod/test/bin/prod-setup
      testuser ALL=(root) NOPASSWD: PROD_NODEKITS
      testuser ALL=(root) NOPASSWD: ALL
      testuser ALL=(ALL) ALL
      testuser ALL=(root) NOPASSWD: PROD_NODESETUP
      Defaults!PROD_NODEKITS !requiretty
      Defaults!PROD_NODESETUP !requiretty


      Then we see something like this:



      # sudo -l -U testuser
      Matching Defaults entries for testuser on <node>:
      always_set_home, secure_path=/usr/sbin:/usr/bin:/sbin:/bin, env_reset, env_keep="LANG LC_ADDRESS LC_CTYPE LC_COLLATE LC_IDENTIFICATION
      LC_MEASUREMENT LC_MESSAGES LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONE LC_TIME LC_ALL LANGUAGE LINGUAS XDG_SESSION_COOKIE",
      !insults

      Runas and Command-specific defaults for testuser:
      Defaults!/opt/org/prod/test/bin/prod !requiretty
      Defaults!/usr/bin/zypper --non-interactive --repo local --no-gpg-checks install org_prod_test.rpm, /usr/bin/zypper --non-interactive
      --repo local --no-gpg-checks install org_prod_pkg1.rpm, /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install
      org_prod_pkg2.rpm, /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install pkg3.rpm !requiretty
      Defaults!/opt/org/prod/test/bin/prod-setup !requiretty

      User testuser may run the following commands on <node>:
      (root) NOPASSWD: ALL
      (ALL) ALL


      I am not sure why specific commands are not getting listed as well as not working with sudo.
      This system is also not having /etc/sudo.conf which might elimates a different sudo plugin being used.



      However, If I do add the /etc/sudoers.d/prodtest_install as provided above on other local SUSE 12 test systems
      there is no issue and I see the following extra lines listed on doing "sudo -l -U testuser":



      User testuser may run the following commands on <local_node>:
      (root) NOPASSWD: /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install org_prod_test.rpm, /usr/bin/zypper
      --non-interactive --repo local --no-gpg-checks install org_prod_pkg1.rpm, /usr/bin/zypper --non-interactive --repo local --no-gpg-checks
      install org_prod_pkg2.rpm, /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install pkg3.rpm
      (root) NOPASSWD: /opt/org/prod/test/bin/prod-setup


      Is there anything that needs to be configured differently on the problematic system/ shoudl I check for something?



      Thanks and warm regards,
      Prasad










      share|improve this question







      New contributor




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











      I am seeing a strange behavior related to sudo on a specific set of systems but not on others.
      I am not sure If there is some specific configuration change required here, which is missing.



      The sudoer configuration is to enable non root users (I have used testuser in below example)
      to install and setup the product packages. The Operating system is SUSE 12.



      Following is the behavior seen on problematic scenario:



      1.) Initially when sudoers is not configured we get something like this:



      # sudo -l -U testuser
      User testuser is not allowed to run sudo on <node>.


      2.) Next if we create the /etc/sudoers.d/prodtest_install file:



      Cmnd_Alias PROD_NODEKITS = /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install org_prod_test.rpm, 
      /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install org_prod_pkg1.rpm,
      /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install org_prod_pkg2.rpm,
      /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install pkg3.rpm
      Cmnd_Alias PROD_NODESETUP = /opt/org/prod/test/bin/prod-setup
      testuser ALL=(root) NOPASSWD: PROD_NODEKITS
      testuser ALL=(root) NOPASSWD: PROD_NODESETUP
      Defaults!PROD_NODEKITS !requiretty
      Defaults!PROD_NODESETUP !requiretty


      Still we see something like:



      # sudo -l -U testuser
      User testuser is not allowed to run sudo on <node>.


      testuser is also not able to use any of the above commands:
      ie. say:



      # sudo /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install pkg3.rpm


      will not work and asks for user passwords and even if we enter passwords the command does not go through.



      3.) But, if we add 2 extra lines "testuser ALL=(root) NOPASSWD: ALL" and "testuser ALL=(ALL) ALL" to allow all commands in /etc/sudoers.d/prodtest_install:



      Cmnd_Alias PROD_NODEKITS = /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install org_prod_test.rpm, 
      /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install org_prod_pkg1.rpm,
      /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install org_prod_pkg2.rpm,
      /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install pkg3.rpm
      Cmnd_Alias PROD_NODESETUP = /opt/org/prod/test/bin/prod-setup
      testuser ALL=(root) NOPASSWD: PROD_NODEKITS
      testuser ALL=(root) NOPASSWD: ALL
      testuser ALL=(ALL) ALL
      testuser ALL=(root) NOPASSWD: PROD_NODESETUP
      Defaults!PROD_NODEKITS !requiretty
      Defaults!PROD_NODESETUP !requiretty


      Then we see something like this:



      # sudo -l -U testuser
      Matching Defaults entries for testuser on <node>:
      always_set_home, secure_path=/usr/sbin:/usr/bin:/sbin:/bin, env_reset, env_keep="LANG LC_ADDRESS LC_CTYPE LC_COLLATE LC_IDENTIFICATION
      LC_MEASUREMENT LC_MESSAGES LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONE LC_TIME LC_ALL LANGUAGE LINGUAS XDG_SESSION_COOKIE",
      !insults

      Runas and Command-specific defaults for testuser:
      Defaults!/opt/org/prod/test/bin/prod !requiretty
      Defaults!/usr/bin/zypper --non-interactive --repo local --no-gpg-checks install org_prod_test.rpm, /usr/bin/zypper --non-interactive
      --repo local --no-gpg-checks install org_prod_pkg1.rpm, /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install
      org_prod_pkg2.rpm, /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install pkg3.rpm !requiretty
      Defaults!/opt/org/prod/test/bin/prod-setup !requiretty

      User testuser may run the following commands on <node>:
      (root) NOPASSWD: ALL
      (ALL) ALL


      I am not sure why specific commands are not getting listed as well as not working with sudo.
      This system is also not having /etc/sudo.conf which might elimates a different sudo plugin being used.



      However, If I do add the /etc/sudoers.d/prodtest_install as provided above on other local SUSE 12 test systems
      there is no issue and I see the following extra lines listed on doing "sudo -l -U testuser":



      User testuser may run the following commands on <local_node>:
      (root) NOPASSWD: /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install org_prod_test.rpm, /usr/bin/zypper
      --non-interactive --repo local --no-gpg-checks install org_prod_pkg1.rpm, /usr/bin/zypper --non-interactive --repo local --no-gpg-checks
      install org_prod_pkg2.rpm, /usr/bin/zypper --non-interactive --repo local --no-gpg-checks install pkg3.rpm
      (root) NOPASSWD: /opt/org/prod/test/bin/prod-setup


      Is there anything that needs to be configured differently on the problematic system/ shoudl I check for something?



      Thanks and warm regards,
      Prasad







      sudo suse






      share|improve this question







      New contributor




      SG Prasad 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




      SG Prasad 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




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









      asked Nov 18 at 7:27









      SG Prasad

      11




      11




      New contributor




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





      New contributor





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






      SG Prasad 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',
          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
          });


          }
          });






          SG Prasad 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%2f482486%2fsudoer-not-allowing-only-all-as-commands-to-user-on-some-systems%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown






























          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








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










           

          draft saved


          draft discarded


















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













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












          SG Prasad 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%2f482486%2fsudoer-not-allowing-only-all-as-commands-to-user-on-some-systems%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