Logfiles do not restrict permissions after rotation

[macladson]

By default we create logfiles with restrict permissions such that only the owner has read/write access. This can help protect sensitive information inside the logfile such as api tokens.

However, after rotation, the new logfile will be made with permissive permissions. The original logfile will be rotated into the next position and keep it's permissions.

So you can end up with a situation like this:

Permissions Size User Date Modified Name
.rw-r--r--  1.0M mac  19 Mar 19:40  beacon.log
.rw-r--r--  1.0M mac  19 Mar 19:39  beacon.log.1
.rw-------  1.0M mac  19 Mar 19:36  beacon.log.2

This may be a bug in our log rotation crate so an upstream solution may be required.