Enforcing socket policy with SELinux












0















I would like to enforce the following SELinux policy:




  • Only the gpsd daemon can bind to TCP port 2947.

  • Any system service running on loopback can be accessed by all local users. No normal user may bind to a port used by a system service.

  • Programs running as distinct, unprivileged, non-system users cannot communicate via loopback TCP sockets.

  • Any user can connect to its own socket.









share



























    0















    I would like to enforce the following SELinux policy:




    • Only the gpsd daemon can bind to TCP port 2947.

    • Any system service running on loopback can be accessed by all local users. No normal user may bind to a port used by a system service.

    • Programs running as distinct, unprivileged, non-system users cannot communicate via loopback TCP sockets.

    • Any user can connect to its own socket.









    share

























      0












      0








      0








      I would like to enforce the following SELinux policy:




      • Only the gpsd daemon can bind to TCP port 2947.

      • Any system service running on loopback can be accessed by all local users. No normal user may bind to a port used by a system service.

      • Programs running as distinct, unprivileged, non-system users cannot communicate via loopback TCP sockets.

      • Any user can connect to its own socket.









      share














      I would like to enforce the following SELinux policy:




      • Only the gpsd daemon can bind to TCP port 2947.

      • Any system service running on loopback can be accessed by all local users. No normal user may bind to a port used by a system service.

      • Programs running as distinct, unprivileged, non-system users cannot communicate via loopback TCP sockets.

      • Any user can connect to its own socket.







      selinux





      share












      share










      share



      share










      asked 9 mins ago









      DemiDemi

      30537




      30537






















          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%2f494355%2fenforcing-socket-policy-with-selinux%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.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f494355%2fenforcing-socket-policy-with-selinux%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

          Can't connect RFCOMM socket: Host is down

          Kernel panic - not syncing: Fatal Exception in Interrupt