chrooted vs non-chrooted postfix: what are realistic security risks?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
0
down vote

favorite












By default, Ubuntu 16 runs postfix chrooted. I know that it is "for security". However, I can not find any documentation for 2 logical questions:



  1. If we change default saslauthd file location, what (specifically) other official Ubuntu packages may be affected? Does saslauthd exist just for postifx, or it has other clients in official Ubuntu repository, and if there are such clients, will they conflict with chrooted postfix?


  2. What are realistic security risks (known attacks ideas) against non-chrooted postifx? By its nature, postfix just listens port 25 and may be 2 other ports, receives and sends emails, but it doesn't interpret any third-party executable code like PHP or Python do, so why will it need chroot at all? In what specific scenarios postfix will interpret executable code or give attacker read or write access to directories not listed in its configuration files?










share|improve this question

























    up vote
    0
    down vote

    favorite












    By default, Ubuntu 16 runs postfix chrooted. I know that it is "for security". However, I can not find any documentation for 2 logical questions:



    1. If we change default saslauthd file location, what (specifically) other official Ubuntu packages may be affected? Does saslauthd exist just for postifx, or it has other clients in official Ubuntu repository, and if there are such clients, will they conflict with chrooted postfix?


    2. What are realistic security risks (known attacks ideas) against non-chrooted postifx? By its nature, postfix just listens port 25 and may be 2 other ports, receives and sends emails, but it doesn't interpret any third-party executable code like PHP or Python do, so why will it need chroot at all? In what specific scenarios postfix will interpret executable code or give attacker read or write access to directories not listed in its configuration files?










    share|improve this question























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      By default, Ubuntu 16 runs postfix chrooted. I know that it is "for security". However, I can not find any documentation for 2 logical questions:



      1. If we change default saslauthd file location, what (specifically) other official Ubuntu packages may be affected? Does saslauthd exist just for postifx, or it has other clients in official Ubuntu repository, and if there are such clients, will they conflict with chrooted postfix?


      2. What are realistic security risks (known attacks ideas) against non-chrooted postifx? By its nature, postfix just listens port 25 and may be 2 other ports, receives and sends emails, but it doesn't interpret any third-party executable code like PHP or Python do, so why will it need chroot at all? In what specific scenarios postfix will interpret executable code or give attacker read or write access to directories not listed in its configuration files?










      share|improve this question













      By default, Ubuntu 16 runs postfix chrooted. I know that it is "for security". However, I can not find any documentation for 2 logical questions:



      1. If we change default saslauthd file location, what (specifically) other official Ubuntu packages may be affected? Does saslauthd exist just for postifx, or it has other clients in official Ubuntu repository, and if there are such clients, will they conflict with chrooted postfix?


      2. What are realistic security risks (known attacks ideas) against non-chrooted postifx? By its nature, postfix just listens port 25 and may be 2 other ports, receives and sends emails, but it doesn't interpret any third-party executable code like PHP or Python do, so why will it need chroot at all? In what specific scenarios postfix will interpret executable code or give attacker read or write access to directories not listed in its configuration files?







      server security email postfix chroot






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Apr 12 at 8:47









      Vitaliy

      1065




      1065

























          active

          oldest

          votes











          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "89"
          ;
          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: true,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1024298%2fchrooted-vs-non-chrooted-postfix-what-are-realistic-security-risks%23new-answer', 'question_page');

          );

          Post as a guest



































          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes















           

          draft saved


          draft discarded















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1024298%2fchrooted-vs-non-chrooted-postfix-what-are-realistic-security-risks%23new-answer', 'question_page');

          );

          Post as a guest













































































          Popular posts from this blog

          pylint3 and pip3 broken

          Missing snmpget and snmpwalk

          How to enroll fingerprints to Ubuntu 17.10 with VFS491