Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-37151

Allow logs to be created with different permissions than data files

    • Type: Icon: New Feature New Feature
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.6.7, 4.0.2
    • Component/s: Logging
    • Labels:
    • Server Security
    • Security 2019-01-14, Security 2019-01-28

      The mongod process creates log files using the same permissions as the underlying data files in the dbpath.

      In some cases, admins or developers are called upon to review issues using the mongod/mongos logs even though they may not have permission to access the data files in the dbpath. The logs and data files all have a mode of either 600 or the mode based on the umask of the underlying process if honorSystemUmask is set.  This is a request to allow for different permissions of the logfiles as opposed to the data files.

      Although it can be argued that the same permissions are needed since the logs can contain sensitive data, this is certainly not the case when the logs are redatced.  In any event, we could allow for the bifurcation of permissions between logs and data as an option, leaving the decision in the customers hands.

            backlog-server-security [DO NOT USE] Backlog - Security Team
            arnie.listhaus@mongodb.com Arnie Listhaus
            0 Vote for this issue
            12 Start watching this issue