[jira] [Commented] (KUDU-1975) glogs are no longer world readable by default

["Adar Dembo (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KUDU-1975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15968219#comment-15968219 ] 

Adar Dembo commented on KUDU-1975:
----------------------------------

I should add that --umask can be used to change Kudu's umask to something more permissive, but that'll affect _all_ files created by Kudu, not just glogs, so it's not really a great workaround for this problem.

> glogs are no longer world readable by default
> ---------------------------------------------
>
>                 Key: KUDU-1975
>                 URL: https://issues.apache.org/jira/browse/KUDU-1975
>             Project: Kudu
>          Issue Type: Bug
>          Components: supportability
>    Affects Versions: 1.3.0
>            Reporter: Adar Dembo
>            Priority: Critical
>
> The fix for KUDU-1855 has a side effect of making all glog files no longer world writable by default. This is because the umask installed by Kudu is 077, which is more restrictive than the typical Linux user default of 022.
> I think this is a regression in supportability, especially given that we've already gone through the trouble to redact sensitive information from the logs (enabled by default).



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