Timeline for How does Certificate Transparance detect fake or forked logs?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 7, 2021 at 8:14 | history | edited | CommunityBot |
replaced https://tools.ietf.org/html/rfc with https://www.rfc-editor.org/rfc/rfc
|
|
| Oct 7, 2021 at 7:24 | history | edited | CommunityBot |
replaced https://tools.ietf.org/html/draft with https://datatracker.ietf.org/doc/html/draft
|
|
| Jan 26, 2018 at 14:04 | history | edited | StackzOfZtuff | CC BY-SA 3.0 |
+agwa blog
|
| Oct 27, 2016 at 14:38 | comment | added | Ajedi32 | I guess theoretically you could run your own Monitor right? Then you'd be able to query that Monitor to verify that a given certificate is included in the log without any risk of compromising your privacy. | |
| Nov 3, 2015 at 9:20 | vote | accept | Tor Klingberg | ||
| Oct 29, 2015 at 16:47 | history | answered | StackzOfZtuff | CC BY-SA 3.0 |