2 ms·

That's not only about Middleboxes (which mostly act up to L4). Most likely it's more about preventing JS from attacking arbitrary servers (e.g. broken mail serv

That's not only about Middleboxes (which mostly act up to L4). Most likely it's more about preventing JS from attacking arbitrary servers (e.g. broken mail servers, file servers, etc) that might have an open TCP port. The "encryption" at least prevents JS attacks from being deterministic.

olliej 8y ago
no, it was specifically due to broken middleware that had existing well known yet unfixed flaws.
aidenn0 8y ago
It was about Application layer middleboxes (specifically broken http proxies).