Timeline for Can ISPs selectively block a page URL on a HTTPS website leaving its other page URLs alone?
Current License: CC BY-SA 4.0
7 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jan 20, 2021 at 12:08 | comment | added | usr-local-ΕΨΗΕΛΩΝ | @FedericoPoloni this is what certificate transparency tries to prevent | |
Jan 19, 2021 at 10:46 | comment | added | jcaron | @FedericoPoloni In theory, if they attempted to use such a root cert in the manner described in the answer at any detectable scale, they would probably get their cert ejected from browsers pretty quickly. Of course, if they do it in a very targeted fashion to stay under the radar... | |
Jan 19, 2021 at 7:35 | comment | added | Federico Poloni | In practice, governments with a better PR office already have root certificates included in the browsers' standard lists, so in principle they could do this without you installing anything. | |
Jan 18, 2021 at 18:42 | comment | added | Joshua | Declaring roots as unusable in the browser code is not a move taken lightly. (Yes, that's what they did.) | |
Jan 18, 2021 at 18:08 | comment | added | Dan Is Fiddling By Firelight | @iBug they've tried at least twice most recently in Dec 2020, but the browser makers just keep responding by refusing to trust the spyware cert. zdnet.com/article/… | |
Jan 18, 2021 at 15:35 | comment | added | iBug | For the record, Kazakhstan attempted to do this back in July (or August?) 2019. | |
Jan 18, 2021 at 14:31 | history | answered | jcaron | CC BY-SA 4.0 |