juju log files should not be world readable

[Kapil Thangavelu]

juju default logs in /var/log/juju are world readable, charms can log sensitive information so a better default would be 600

[Mario Splivalo (mariosplivalo)]

Would it be possible to have local provider world-readable log files? Or at least set them to adm (or juju?) group, and have them group-readable?
Local provider is used mainly for testing charm development and it's cumbersome to type in sudo password all the time, or to have root terminal permanently open.
Or, maybe add a juju environment configuration option so that one can 'ease up' on the default (for instance, default chmod is 600, but user can change that to 640 or 644).

[Matt Bruzek (mbruzek)]

With this change landing now I have to use sudo to look at the log files.

As a charmer I often look at the unit-charm-name-0.log file for more details of what the charm is doing.

The log file change makes it more difficult for charm authors to look at the logs on their local system to debug the charm.

Could we do better with some ownership or group changes?

[Kapil Thangavelu (hazmat)]

once debug-log gets unbroken that might be viable as go to resource for log
info, else group usage might help. for local its a bit unclear though.

On Tue, Sep 23, 2014 at 12:26 PM, Matt Bruzek <email address hidden>
wrote:

> With this change landing now I have to use sudo to look at the log
> files.
>
> As a charmer I often look at the unit-charm-name-0.log file for more
> details of what the charm is doing.
>
> The log file change makes it more difficult for charm authors to look at
> the logs on their local system to debug the charm.
>
> Could we do better with some ownership or group changes?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1286518
>
> Title:
> juju log files should not be world readable
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1286518/+subscriptions
>