#141: expanding audit description Changes (by [email protected]):
* owner: [email protected] => [email protected] Comment: From issue #134 which I've just merged to this one: "Section 12 says that TLS clients can use logs and SCTs to reduce the likelihood that they will accept misissued [sic] certificates. Since direct access to a log to acquire an inclusion proof is viewed as bad from a privacy perspective, it’s not clear what sort of log access by a client is being suggested here. This needs to be clarified, or just removed." Point out there are privacy implications of clients directly communicating with logs, which the use of proxies can alleviate. -- --------------------------+------------------------------- Reporter: [email protected] | Owner: [email protected] Type: defect | Status: new Priority: major | Milestone: Component: rfc6962-bis | Version: Severity: - | Resolution: Keywords: | --------------------------+------------------------------- Ticket URL: <https://trac.tools.ietf.org/wg/trans/trac/ticket/141#comment:4> trans <https://tools.ietf.org/trans/> _______________________________________________ Trans mailing list [email protected] https://www.ietf.org/mailman/listinfo/trans
