3 ms·
It would be very good for the net if something came up that penalised middleboxes though. Maybe this could be it.
by fulafel 9y ago
It would be very good for the net if something came up that penalised middleboxes though. Maybe this could be it.
- lumisota 9y agoQUIC demonstrates a better approach: encrypt everything, limiting the ability for middleboxes to make assumptions about behaviour.
- kevincox 9y agoEven QUIC found that the couple of bytes of "flag" fields in the header were enough for middleboxes to mess with it. It seems incredibly hard to devise a protocol which is extensible without having middleboxes mess it up.
- lumisota 9y agoIndeed. Though that issue sort of validated the approach: middlebox vendors will latch on to any unencrypted bits they can. The only way to stop that is to encrypt _everything_.
- zrm 9y ago> It would be very good for the net if something came up that penalised middleboxes though. What you can do is to have a good protocol that requires no interference from middleboxes but detects it if it happens, and then a less efficient legacy fallback protocol that basically looks as much as possible like HTTPS. Then if you detect interference from a middlebox, show the user a message that says, "WARNING: MAN IN THE MIDDLE ATTACK DETECTED. Something is modifying connections on this network. This may compromise security and performance." Then hopefully having multiple different apps show a message like that to every user on the network will get enough users complaining to fix the middlebox so that it stops breaking new things.