Timeline for Organisation's use of SSL inspection and duplication of root CA certs
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 12, 2017 at 20:49 | history | tweeted | twitter.com/StackSecurity/status/918579379546001408 | ||
| Oct 12, 2017 at 19:50 | answer | added | ste-fu | timeline score: 0 | |
| Oct 12, 2017 at 18:22 | answer | added | Mike Ounsworth | timeline score: 2 | |
| Oct 12, 2017 at 18:13 | history | edited | Mike Ounsworth |
edited tags
|
|
| Oct 12, 2017 at 16:03 | answer | added | symcbean | timeline score: 0 | |
| Oct 12, 2017 at 15:52 | comment | added | Ajedi32 | I'd probably treat it like any other security vulnerability and practice responsible disclosure. (Even though in this case the vulnerability is essentially by design.) Then once the school refuses to fix the problem (I'm guessing that's probably what will happen), your only recourse will be public shaming. (I.E. Informing others of the risks of using the school's network, and advising they avoid it for that reason.) | |
| Oct 12, 2017 at 15:25 | review | First posts | |||
| Oct 12, 2017 at 15:41 | |||||
| Oct 12, 2017 at 15:21 | history | asked | Adam W | CC BY-SA 3.0 |