Timeline for Security implications of allowing websites to open TCP sockets
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 31, 2018 at 7:58 | history | tweeted | twitter.com/StackSecurity/status/958610357572067328 | ||
| Jan 30, 2018 at 23:29 | vote | accept | Qwertie | ||
| Jan 30, 2018 at 5:37 | comment | added | Steffen Ullrich | related or maybe duplicate Why no support for TCP Sockets in JavaScript. | |
| Jan 30, 2018 at 5:12 | answer | added | Steffen Ullrich | timeline score: 6 | |
| Jan 30, 2018 at 3:03 | comment | added | forest | A comment on one of those answers linked to w3.org/TR/raw-sockets/#security-and-privacy-considerations, which gives information about the risks of a raw socket API. Are you are talking about plain TCP sockets, or raw sockets themselves? | |
| Jan 30, 2018 at 2:58 | history | asked | Qwertie | CC BY-SA 3.0 |