kenzaki
Member
- Downloaded
- 63.8 GB
- Uploaded
- 23.6 GB
- Ratio
- 0.37
- Seedbonus
- 30
- Upload Count
- 0 (0)
Member for 7 years
Yo bro, Good Day! Before I post or share this one, I tested it for many times with my own pc/other pc's and it seems working well.This goes to all of us.
Even tho this is a necro thread from 2018 its a good opportunity to bring this to our attention. Please, before anyone posts things about how to do this and that, do research on what exactly is the change supposed to do, where does it apply, and if there are any risks.
First of all, for Quic to work both client and server/site must support it, and to my knowledge quic hasn't been adopted yet, not by the majority of sites. Second, the main advantage of QUIC is that it offers better performance for users connected to slow networks and ones with packet loss and high latency. It doesn't affect as much, users on modern/current internet lines. When quic says "faster" it doesn't mean you will get more megabytes out of your line but rather you will have a bit lower delays (if you have any) for when the site responds to your actions. Essentially it will minimize the time it takes from click to action.
The bad news:
Nothing tho comes without a risk. Quic is using UDP instead of TCP to establish data communication. Modern firewalls, software, or hardware and modems are not designed to use UDP for HTTP data and only check TCP which essentially means it's like you are not using any firewall when you enable the QUIC option and visit a Quic enabled site. So here is my question, would any of you visit a site that asked you to switch off your firewall? No. But that's what you do in this case.
In most architectures, when HTTP traffic is detected, it is passed on to a web protection module that performs web filtering, deep packet inspection etc. HTTP traffic gets special treatment because the firewalls can interpret the traffic from Layer4 up to layer 7. This special treatment includes malware scanning and in most cases, enhanced reporting etc.
QUIC uses the traditional HTTP ports of 80 and 443 but that is where the similarities end. The supporting browsers and servers support this new protocol and are able to process it as web traffic, but the network device in between cannot determine the application protocol and switches to treating it like any generic layer 4 UDP traffic. QUIC traffic is therefore not checked as it should be and it is not forwarded to the firewall’s web protection features.
The real world implications of QUIC traffic, range from not being able to restrict access to sites and apply some firewall rules, or even enforce Safe Search, through to malware or ransomware being downloaded through Gmail or any other QUIC enabled website since your firewall/scanners that are in the middle wont understand them as normal HTTP traffic.
The above of course is a short analysis and I don't mean that this will always be the case. Things over time may improve or we will all just move to hhtp/3 but please don't just believe anything you see on the internet. Specially for the posters, you have a responsibility to the people that read your posts. Always try to find negative/positives and state them in your thread so people can make an informed decision.