Timeline for Does SSL/TLS (https) hide the urls being accessed
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 10, 2018 at 18:19 | comment | added | Paŭlo Ebermann | @everydayjoe thanks for the edit proposal, but I don't think it is needed here. It is also already incorporated into other answers. | |
| Jul 10, 2018 at 18:11 | review | Suggested edits | |||
| Jul 10, 2018 at 18:18 | |||||
| Dec 28, 2016 at 8:56 | comment | added | usr-local-ΕΨΗΕΛΩΝ | To keep it short: if you visit a certain NSFW URL anyone in the line can know you connected to that site at that time, but no one can know the NSFW content you requested | |
| Jul 29, 2016 at 14:41 | comment | added | Tom | securityweek.com/hackers-can-intercept-https-urls-proxy-attacks | |
| Oct 3, 2011 at 7:21 | vote | accept | Jus12 | ||
| Sep 30, 2011 at 19:40 | history | edited | Paŭlo Ebermann | CC BY-SA 3.0 |
add disclaimer about the length and server name, adding links
|
| Sep 29, 2011 at 13:20 | comment | added | Thomas Pornin | Also, the server name is included in the certificate that the server sends back to the client as part of the handshake, and that certificate is sent "in the clear" -- so the target server name is really not secret at all. | |
| Sep 29, 2011 at 13:16 | history | migrated | from crypto.stackexchange.com (revisions) | ||
| Sep 29, 2011 at 13:15 | history | answered | Paŭlo Ebermann | CC BY-SA 3.0 |