On Wed, Jun 10, 2015 at 10:53:30AM +0100, Rob Stradling wrote: > On 10/06/15 01:54, Matt Palmer wrote: > >A log has a single well-defined purpose, and I don't think that adding > >independent > >functionality to the purpose of the log itself is a winning strategy. > > Indeed. A log and a monitor are separate software components. > > Sorry I was unclear. I was imagining that a provider might want to provide > both a log and a monitor for that log, running from the same server, using a > shared database. (IMHO, we shouldn't require this, but we shouldn't > prohibit it either).
I must say, I'd never thought that anyone would try to forbid an entity running a log from also running a monitor. Its value, at least insofar as it is attempting to detect malfeasance of the log operator, may be quite limited, but that's for the users of the monitor service to decide for themselves. - Matt _______________________________________________ dev-security-policy mailing list dev-security-policy@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-security-policy
