You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2017/05/18 01:12:04 UTC

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

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

Todd Lipcon commented on KUDU-1975:
-----------------------------------

I'm inclined to close this as wontfix... last chance to argue? :)

> 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)