|
|
|
|
|
by parliament32
2218 days ago
|
|
Exactly. This isn't websockets specific, you can portscan happily with pure JS. The issue is that browsers are allowing connections (from untrusted code) to private/loopback address space. This should really be behind a permission. |
|