[
https://issues.apache.org/jira/browse/KUDU-1975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adar Dembo resolved KUDU-1975.
------------------------------
Resolution: Won't Fix
Fix Version/s: n/a
bq. I'm inclined to close this as wontfix... last chance to argue?
I've since talked to colleagues who feel as you do (that logs should be "secure
by default") and changed my mind.
> 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
> Fix For: n/a
>
>
> 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)
