[
https://issues.apache.org/jira/browse/LOG4J2-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064593#comment-16064593
]
ASF GitHub Bot commented on LOG4J2-1699:
----------------------------------------
GitHub user phymbert opened a pull request:
https://github.com/apache/logging-log4j2/pull/89
[LOG4J2-1699] Log File Permissions with PosixFilePermission feedback from
jira
item 2: Better log at configuration step if file attribute view are defined
but underlying files system doesnt support it
item 3: Exception catch and logged if OperationNotSupported or Operation
not permitted are thrown while changing file attribute permissions, user or
group
item 4: No need to apply file posix attribute if file is just rolled not
compressed, both in DirectWriteRolloverStrategy and DefaultRolloverStrategy.
Changed next release version in documentation and javadoc.
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/89.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 #89
----
commit 38e0becb1ac0ef01b8197931e08575ed1cb44387
Author: phymbert <[email protected]>
Date: 2017-06-27T09:18:26Z
[LOG4J2-1699] No need to apply file posix attribute if file is just
renamed not compresed
commit ecba42b570ff3451a5fbbf46b153f2fb8fe4886e
Author: phymbert <[email protected]>
Date: 2017-06-27T09:35:22Z
[LOG4J2-1699] Change wrong target version release, 2.8.3 to 2.9 in
javadoc and documentation
Signed-off-by: phymbert <[email protected]>
commit 347db2a74532f37f498369da5c1e906a7a4ae7c1
Author: phymbert <[email protected]>
Date: 2017-06-27T09:51:47Z
[LOG4J2-1699] Use status logger to warn if posix file attribute view are
defined but underlying files system doesnt support it.
Signed-off-by: phymbert <[email protected]>
commit de82a825ca10f9c9314a18798a024fc71e5911ba
Author: phymbert <[email protected]>
Date: 2017-06-27T10:01:41Z
[LOG4J2-1699] Catch and log if applying attribute view throws exception.
More comprehensible field/method name.
Signed-off-by: phymbert <[email protected]>
commit b8a817047aed0432bf229558118587383e490187
Author: phymbert <[email protected]>
Date: 2017-06-27T10:08:49Z
[LOG4J2-1699] Update some comments and error message.
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)
