[
https://issues.apache.org/jira/browse/LOG4J2-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16059266#comment-16059266
]
ASF GitHub Bot commented on LOG4J2-1699:
----------------------------------------
GitHub user phymbert opened a pull request:
https://github.com/apache/logging-log4j2/pull/83
[LOG4J2-1699] Refactor PosixFileAttributeViewAction with Builder. Fix posix
tests on jenkins.
Refactor PosixFileAttributeViewAction with Builder rather than method
factory. Split posix tests inner static classes to 2 differents test class
files because it doesnt run on jenkins. Add a static method in FileUtils to
check if posix file attribute view is supported in order to log if posix
attributes are defined
but the filesystem doesnt support it. Fix when user has only one group in
the test case.
Signed-off-by: phymbert <[email protected]>
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/phymbert/logging-log4j2 LOG4J2-1699
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/logging-log4j2/pull/83.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #83
----
commit 64c55f2b60d1a22e948969582c0779e630b728c1
Author: phymbert <[email protected]>
Date: 2017-06-22T12:13:54Z
[LOG4J2-1699] Refactor PosixFileAttributeViewAction with Builder rather
than method factory. Split posix tests inner static classes to 2
differents test class file because it doesnt run on jenkins. Add a
static method in FileUtils to check if posix file attribute view is
supported. It will allow later to log if posix attributes are defined
but the file system doesnt support them. Fix when user has only one
group in the test case.
Signed-off-by: phymbert <[email protected]>
----
> 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.9
>
> Attachments: LOG4J2-1699-2.patch, LOG4J2-1699.patch
>
> 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.4.14#64029)
