Though, reading the implementation… 1. I’m not co...
# core
s
Though, reading the implementation… 1. I’m not convicned the database files should be writable by the osquery group 2. umask in the init script feels weird. Can we do this in the code?
t
Yes we can implement the umasking-behavior in code but it seems OK that it's in the systemd unit. Perhaps the only issue is the init script?
s
My comment applies to systemd, and init equally.
t
It's a feature of an exec unit in systemd (thus I am assuming it's expected) https://www.freedesktop.org/software/systemd/man/systemd.exec.html
s
What about the next thing? It feels like it’s adding some logic to the start script. which feels weird. It also means that the socket and the db files have the same meaning
t
expected = a thing that happens maybe
there's no permissions boundary between socket and db so thats OK
s
This is all a weak objection. If people would rather have osquery just respect umask, I’m super opposed. Mostly just feels weird.
t
If people would rather have osquery just respect umask, I’m super opposed.
what do you mean?
s
Exactly the opposite. Clearly too distracted. If people want to just respect umask. I’m onboard.
t
ah ok 🙂
I'll just escalate the code review to #linux ;)
s
FYI you want @-here, @-channel gets idle people too.