28 ms·
This is about a university, not the NSA. Sure, there are other security measures you need to take (known botnets etc.) but a blanket ban on all outgoing network
by jeroenhd 4y ago
This is about a university, not the NSA. Sure, there are other security measures you need to take (known botnets etc.) but a blanket ban on all outgoing network traffic? That's just excessive.
This isn't the first post the author has made about their university's network infrastructure. The HTTP/3 issues start being named years back.
The university, as an organisation, doesn't seem to want to move away from the old way of doing networking. There's no indication this is a "we have to hotfix it for now because our new systems are done in 2030" network, and every indication that they're stretching their current design for as long as it'll hold.
Even if they're doing this for security reasons, the days of unsecured bastions with a strict firewall around them, as suggested by their latest infrastructure blog post, are long gone. I highly doubt security is the reason the university can't move on.
With no migration plans as far as I can see, they're setting themselves up for failure again when HTTP/4 inevitably comes around, or when strict networking peculiarities cause the next QUIC/HTTP3/TLS 1.3 bug the author will have to dive into and figure out.