You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Gary Gregory (JIRA)" <ji...@apache.org> on 2016/11/12 07:01:07 UTC
[jira] [Comment Edited] (LOG4J2-1699) Configurable Log File
Permissions
[ https://issues.apache.org/jira/browse/LOG4J2-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15659174#comment-15659174 ]
Gary Gregory edited comment on LOG4J2-1699 at 11/12/16 7:00 AM:
----------------------------------------------------------------
So this is about calling {{java.nio.file.Files.setPosixFilePermissions(Path, Set<PosixFilePermission>)}} at just the right time.
It might also be interesting to have a separate ticket for {{java.nio.file.Files.setOwner(Path, UserPrincipal)}}.
Give it a go :-)
was (Author: garydgregory):
So this is about calling {{java.nio.file.Files.setPosixFilePermissions(Path, Set<PosixFilePermission>)}} at just the right time.
It might also be interesting to have a separate ticket for {{java.nio.file.Files.setOwner(Path, UserPrincipal)}}.
> Configurable Log File Permissions
> ---------------------------------
>
> 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
>
> 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.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org