----- Original Message -----
> On 03/07/13 14:06, Nathan Scott wrote:
> > ...
> pmlc>
>
> Any legal combination of {mandatory,advisory} x {on,off} should be valid
> for pmlogger and understood by pmlc ... if not it is a bug.
And... its passing for me too now, not sure what happened there,
but something else seems to have fixed it up.
> > Also, when pmlogconf generates a configuration file initially (so,
> > when no pre-existing one found where specified) I've changed it to
> > add a default [access] section - could you review that too please?
> > Have attempted to specify no-remote-access-allowed-by-default, and
> > also no-local-changes-allowed-by-default.
>
> Why no local changes by default? at first blush I'd expect
>
> allow localhost : all;
>
> like pmcd.conf.
>
I was a bit concerned with anyone having a local login being able to
effectively prevent the default logger from logging - that seems like
it needs to be blocked?
e.g. perhaps a school/uni scenario, students might want to maliciously
stop logging of network traffic at certain times while they run torrent
servers or gaming servers or something like that.
cheers.
--
Nathan
|