[
https://issues.apache.org/jira/browse/KUDU-3208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17222677#comment-17222677
]
Alexey Serbin edited comment on KUDU-3208 at 10/29/20, 3:35 AM:
----------------------------------------------------------------
Just two cents from my side: there is {{\-\-logfile_mode}} flag to control glog
file permissions (it seems not be able to read values in octal notation), but
it's also affected by {{--umask}} setting (and that's sort of expected).
But indeed, it would be great to make an option for {{\-\-logfile_mode}} to be
not affected by {{--umask}}. I'm not sure how to implement that without
compromising the security of other files created by a process, though if not
using a direct call to {{chmod()}} right after creating a file with {{open()}}
if umask is in effect. But {{\-\-logfile_mode}} is a flag from glog
third-party library, so it would require patching the glog library to add this
soft of workaround.
was (Author: aserbin):
Just two cents from my side: there is {{--logfile_mode}} flag to control glog
file permissions (it seems not be able to read values in octal notation), but
it's also affected by {{--umask}} setting (and that's sort of expected).
But indeed, it would be great to make an option for {{--logfile_mode}} to be
not affected by {{--umask}}. I'm not sure how to implement that without
compromising the security of other files created by a process, though.
> Separate umask for log dir
> --------------------------
>
> Key: KUDU-3208
> URL: https://issues.apache.org/jira/browse/KUDU-3208
> Project: Kudu
> Issue Type: Improvement
> Components: security
> Affects Versions: 1.13.0
> Reporter: Peter Ebert
> Priority: Major
>
> Currently the umask is applied to all directories/files kudu manages. Logs
> are typically less sensitive and could be 744 (as they are with HBase by
> default), which enables teams to debug issues that may not have root/kudu
> keytab access.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
