Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Developers List" <log4j-dev@logging.apache.org>
Date: Fri, 3 Mar 2017 19:11:46 +0000 (UTC)
From: "Ralph Goers (JIRA)" <jira@apache.org>
To: log4j-dev@logging.apache.org
Message-ID: <JIRA.13020249.1478928511000.57763.1488568306860@Atlassian.JIRA>
In-Reply-To: <JIRA.13020249.1478928511000@Atlassian.JIRA>
References: <JIRA.13020249.1478928511000@Atlassian.JIRA> <JIRA.13020249.1478928511080@jira-lw-us.apache.org>
Subject: [jira] [Updated] (LOG4J2-1699) Configurable Log File Permissions
 with PosixFilePermission
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 03 Mar 2017 19:11:53 -0000


     [ https://issues.apache.org/jira/browse/LOG4J2-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralph Goers updated LOG4J2-1699:
--------------------------------
    Fix Version/s:     (was: 2.8.1)
                   2.8.2

> Configurable Log File Permissions with PosixFilePermission
> ----------------------------------------------------------
>
>                 Key: LOG4J2-1699
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1699
>             Project: Log4j 2
>          Issue Type: Question
>          Components: Appenders
>         Environment: Linux
>            Reporter: Demetrios Dimatos
>            Priority: Critical
>              Labels: features
>             Fix For: 2.8.2
>
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> We would like to hear the communities thoughts on being able to configure the permissions log files are created with. We don't want to rely on UMASK because we have managed services who's process should generate logs with a 644 yet deployed applications by users should default to a 640 because the logs may contain sensitive information.
> We will make the modification and set this in the properties file. Now we are looking to see what the community position would be on accepting such a patch, we don't want to be patching our own distribution indefinitely. 
> I searched all the JIRAs and was not able to find any matching requirements recently. All I could find was something dated in 2006: https://bz.apache.org/bugzilla/show_bug.cgi?id=40407


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org