Ben,
...
This is true even if you use hashes, surely? For example, an old key
(from a log no longer known to someone) could be reused. Or a key for
a log that was never used publicly. Or the same key could be used for
two logs accepted by different clients. And so on.
I would expect a Monitor to keep track of the public key for each log
operator
that it watches, (but that should be stated explicitly). Thus re-use of
an old key
by that log operator, for a new log instance, would be detected easily
if the log
ID were derived from the public key. The most common case, if the re-use
is accidental,
is probably starting a new log instance but not remembering to change
the key. That would
be obvious/impossible if the ID were derived from the key.
However, I agree that a log re-using a key from some other log would not be
detected by this approach.
Steve
_______________________________________________
Trans mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/trans
