Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-116

Do not run maxscale as root.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.1.0
    • Fix Version/s: 1.2.0
    • Component/s: Core
    • Labels:
      None

      Description

      This is really poor manners.
      I'm not sure if there's a reason for it other than this has not been looked at but please consider:

      • not allowing maxscale to run as the root user
      • if running as the root user, dropping privileges to a different user (maxscale?) that's configured for example in MaxScale.cnf
      • this should pretty much match the behaviour of MySQL or MariaDB, and it prevents possible exploits should something break in the code.

      [note: you need a component: Generic and a Versions: All versions]

        Attachments

          Issue Links

          relates to

          Sub-Task - The sub-task of the issue MXS-157 Test Non-root execution

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MXS-24 bugzillaId-604: Module load path documentation issues ...

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Task - A task that needs to be done. MXS-133 Testing MaxScale 1.2.0 Features

          • Major - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              markus makela markus makela
              Reporter:
              simon.mudd Simon J Mudd
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.