Skip to content

Logfile compression bypasses restricted permissions #52

@macladson

Description

@macladson

I only noticed this after #51 was merged, but when building a file logger, if both restrict_permissions and compress are set, the logfile is initially created with umask of 600 but upon compression, the compressed files are set to 644.

I suspect this is because unlike the regular file rotation which simply renames the files in place (leaving any existing permissions intact), compression creates a new file (with a new set of permissions) which the contents of the log file are then written into.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions