4
edits
CA/CT Redaction: Difference between revisions
Jump to navigation
Jump to search
→Alternatives to Redaction: add comment for some of alternatives
(→Logging Reveals Commercially Sensitive Information: this one was not for domain-label-name redaction, but for name-constrainted intermediate) |
(→Alternatives to Redaction: add comment for some of alternatives) |
||
| Line 127: | Line 127: | ||
* Disabling CT via browser policy in enterprises | * Disabling CT via browser policy in enterprises | ||
* Private roots | * Private roots | ||
**As the number of IoT devices increases, number of private roots would increase as well. Managing many private roots is expected to put a burden on users | |||
* Wildcard certs | * Wildcard certs | ||
* Log a name-constrained intermediate | * Log a name-constrained intermediate | ||
**As a one of "redaction mechanism", this mechanism was removed from RFC6962-bis with “domain label name-redaction”. Currently, there is not any specification for this mechanism. | |||
* CT-logging anyway | * CT-logging anyway | ||