Where is pfSense support for HTTP/3 and QUIC protocol support?

johnpoz

@lohphat said in Where is pfSense support for HTTP/3 and QUIC protocol support?:

pfSense doesn't support wildcard domain aliases

Nothing supports a wildcard domain alias - because its pretty much an infinite possible amount of IPs.

If you want to filter on user trying to go to wildcard.domain.tld you would need to do a proxy..

But a firewall that blocks on a wildcard aliases isn't a thing.. What you could have is some firewall that did a query on whatever fqdn a user is trying to resolve and let that resolve or not, You can do that now with pfsense and unbound.. If you don't want user to go to wildcard.domain.tld then don't let him resolve domain.tld.

Firewall rules are based on IPs - it is impossible to resolve every IP in an infinite alias.. So you would need to control if that can even be attempted to be resolved which is dns, not the actual firewall that allows or blocks on an IP, etc.

lohphat

@johnpoz said in Where is pfSense support for HTTP/3 and QUIC protocol support?:

But a firewall that blocks on a wildcard aliases isn't a thing.. What you could have is some firewall that did a query on whatever fqdn a user is trying to resolve and let that resolve or not, You can do that now with pfsense and unbound.. If you don't want user to go to wildcard.domain.tld then don't let him resolve domain.tld.

I understand that.

A proxy may be the answer, but I can also envision is a rule which can be specified to do a reverse lookup and if the returned FQDN is within the permitted wildcard, then permit it. And instead of doing this for every request have a tunable cache of IP to reverese lookup names to speed up subsequent requests.

Essentially it's a reverse concept to pfBlocker but for a specific permit rule.

johnpoz

@lohphat said in Where is pfSense support for HTTP/3 and QUIC protocol support?:

I can also envision is a rule which can be specified to do a reverse lookup and if the returned FQDN is within the permitted wildcard

Great and not all IPs even have a PTR.. So this system might work or might not work.. PTRs don't always list the "domain" etc.. could just be a generic name for the IP and what part of the world its in, etc

So now you want your "firewall" to do a PTR query on every single hit of traffic that wants to go through the firewall.. That is going to be a shit ton of dns queries, where most of them as far as PTRs go wont even resolve to anything..

;; QUESTION SECTION:                                                                
;www.amazon.com.                        IN      A                                   
                                                                                    
;; ANSWER SECTION:                                                                  
www.amazon.com.         30      IN      CNAME   tp.47cf2c8c9-frontier.amazon.com.   
tp.47cf2c8c9-frontier.amazon.com. 30 IN CNAME   d3ag4hukkh62yn.cloudfront.net.      
d3ag4hukkh62yn.cloudfront.net. 30 IN    A       99.84.166.43                        

;; QUESTION SECTION:
;43.166.84.99.in-addr.arpa.     IN      PTR

;; ANSWER SECTION:
43.166.84.99.in-addr.arpa. 82726 IN     PTR     server-99-84-166-43.ord52.r.cloudfront.net.

lohphat

@johnpoz said in Where is pfSense support for HTTP/3 and QUIC protocol support?:

So now you want your "firewall" to do a PTR query on every single hit of traffic that wants to go through the firewall.. That is going to be a shit ton of dns queries, where most of them as far as PTRs go wont even resolve to anything..

Not at all, the overhead would be incurred not for all traffic but for a specific rule requesting the reverse lookup (e.g. UDP/443 requests only), and caching the results to reduce the need for a reverse lookup for each request.

I know PTRs are not required and may not match but it's what we have available and the larger CDNs I'm trying to target (Google, MSFT, et al) usually (not always) have more consistent DNS records.

johnpoz

@lohphat Can't wait for you to come out with this magic firewall of yours.. Since clearly pfsense is just not doing it right..

Free as well like pfsense I assume.

lohphat

@johnpoz

Aug 4 09:11:16 LAN QUIC HTTP/3 (1659322461)[2603:xxxx::1d04]:49375
[2607:f8b0:4006:823::200a]:443
lga34s39-in-x0a.1e100.net

So in the case of YouTube, the destination address DID resolve into a sane FQDN

johnpoz

@lohphat said in Where is pfSense support for HTTP/3 and QUIC protocol support?:

into a sane FQDN

but is not the domain user was trying top go to - so where is this list pfsense is magic going to have that says oh if user looks up domainX something, and the PTR comes back otherdomainY or somethinG or xyzdomainX then sure let it through..

How does this magic firewall even know that IP 1.2.3.4 should have a ptr done on it and only if in its list of ok domains should it be allowed.

So any destination IP using udp 443, it should do a ptr on and only allow from your list of domains that are permitted. Who is compiling this list of PTR domains that are ok? How is it going to be updated?

What if going to udp 8443, what about udp 10443, or 4430, etc.. Just block all those? Or should it do PTR queries on the IPs

lohphat

@johnpoz said in Where is pfSense support for HTTP/3 and QUIC protocol support?:

@lohphat Can't wait for you to come out with this magic firewall of yours.. Since clearly pfsense is just not doing it right..

Free as well like pfsense I assume.

I don't think the snark is necessary.

Having a method to trigger an additional address verification for a specified rule -- and not all traffic (I don't know where you got that impression I was suggesting that) -- doesn't seem impossible or need to "create a new firewall".

lohphat

@johnpoz said in Where is pfSense support for HTTP/3 and QUIC protocol support?:

@lohphat said in Where is pfSense support for HTTP/3 and QUIC protocol support?:

into a sane FQDN

but is not the domain user was trying top go to - so where is this list pfsense is magic going to have that says oh if user looks up domainX something, and the PTR comes back otherdomainY or somethinG or xyzdomainX then sure let it through..

You're not getting the point -- AT ALL.

I want to PERMIT google UDP/443 requests for YouTube.
I know that Google uses *.1e100.net for most if not all their YT content.
I want a rule to check if the UDP/443 destination address is within *.1e100.net
For THIS RULE, take the time to reverse lookup the destination FQDN and cache it for any subsequent requests, and match the domains in the permit rule.
For ALL OTHER UDP/443, drop.

@johnpoz said in Where is pfSense support for HTTP/3 and QUIC protocol support?:

but is not the domain user was trying top go to - so where is this list pfsense is magic going to have that says oh if user looks up domainX something, and the PTR comes back otherdomainY or somethinG or xyzdomainX then sure let it through..

I have no idea where you got this from. I never suggested this was the use case.

johnpoz

@lohphat said in Where is pfSense support for HTTP/3 and QUIC protocol support?:

I know that Google uses *.1e100.net for most if not all their YT content.

How do you know this - where does pfsense learn this from... You going to manually put that in? What if google now starts having ptrs that resolve with new1e200.net etc..

Where is this info going to come from - who is going to put it in to the firewall, how is it going to be updated and maintained as it changes, etc.

And you want this only for quic but not tcp - because why exactly? The same stuff that can happen over quic can happen over tcp 443..

So pfsense should also do all this over tcp 443 as well..

Lets say you query when user hits udp 443 going to 1.2.3.4 - how fast does that ptr resolve? What if takes longer than normal, clients hasn't got an answer and has already sent 3 retrans - oh well guess I can't get there - sorry user.. Try again later in his browser window.

lohphat

@johnpoz said in Where is pfSense support for HTTP/3 and QUIC protocol support?:

@lohphat said in Where is pfSense support for HTTP/3 and QUIC protocol support?:

I know that Google uses *.1e100.net for most if not all their YT content.

How do you know this - where does pfsense learn this from... You going to manually put that in? What if google now starts having ptrs that resolve with new1e200.net etc..

Where is this info going to come from - who is going to put it in to the firewall, how is it going to be updated and maintained as it changes, etc.

And you want this only for quic but not tcp - because why exactly? The same stuff that can happen over quic can happen over tcp 443..

So pfsense should also do all this over tcp 443 as well..

I wasn't suggesting pfSense do this automatically -- ME THE ADMIN determines the domains to permit. If things change over time, I WILL MAKE THE CHANGES.

I just want the functionality of being able to do this.

This is no different than blocking/permitting any other website -- or any other protocol.

What's missing is wildcard domain aliases and I think this is a solvable problem so that admins have the choice to use it -- or not. If they try to do this on too many requests then yes, the f/w will slow.

But I'm not suggesting ANYONE do that, I just want some way to OPTIONALLY add an additional reverse lookup -- and cache the result -- to then use in a rule.

That doesn't seem unreasonable.

JonathanLee

@lohphat QUIC protocol has been in the works for some time now Google and Facebook want to use it. PaloAlto is also a firewall company has even released an update that can detect QUIC traffic. New protocols have to be approved before getting used. For now, I only allow TCP traffic to 443. It was created to help speed up streaming traffic and it was experimental for sometime. Just block it and the traffic defaults back to TCP.

lohphat

@jonathanlee I understand all that. But the protocol has now been ratified by the IETF and thus having some level of control other than all or nothing is desirable. Being able to whitelist QUIC from well-known sources and not others seems a reasonable middle-ground. I want YouTube and Google data streamlined but not from any random site.

JonathanLee

@lohphat Palo Alto recently gained capacity last year for appID to see what the traffic is. Firewalls do have the ability. Give it time PfSense will soon have that ability as well.

I did a discussion post about this in Firewall class while working on my AA. As Facebook turned it on when I was working with Palo Alto images for assignments the Professor said that it is normal to block the UDP 443 traffic unless it is required.

URL blocking and items will be a problem if you let HTTPS3 run. Facebook started tested HTTPS3 today and now is only using this with my IP address. Hypothetically if a triad of major IT companies all start using HTTPS3 at once, example being Google, Facebook, and Cisco. Firewall companies are forced to react. The real question is what is the proper guidelines for security controls and use of HTTPS3 in firewalls. Over many years in the field I have seen this tactic done to force major sales. One can forecast a new product will come out after that protocol is staged for major use. Again, hypothetically, "Cisco's New ____" fill in the blank. ASA with QUIC controls for example. Understanding the movements and planning is important I feel in cybersecurity. Watch out for this protocol. When I worked at NCR we had products that were only allowed to be used with one vendor per contract for a specific amount of years, and no one else. So Google's HTTPS3 proprietary protocol could be licensed to only one firewall vendor for decryption for a specific timeline of for example 5 years maybe Palo Alto could have the decryption rights for it. It is the gray areas we need to watch out for. Investments and the sole investors into the new products get first dibs on such items explicitly. The real question comes back to, what is the Federal Government Guidelines for such a triad of issues Firewalls, Protocols, and Approval of Use.

Again to look at this within security and corporate network issues, Obscurity is of upmost importance when working with exploits. Antivirus software is finetuned daily to detect specific exploits within the signatures of files. Encoders play a key role in obfuscation for the security of the exploit and it's handlers. Use of encoders gives rise to polymorphism within code, code that is ever changing in its location and signature. To put in other words this is so new that it has not been hardened enough to be left wide open with a firewall. Follow the recommendations until they approve of it's use for secure networks. Nation state actors love the grey areas. For now only allow 443 and 80 with tcp, until explicitly advised that it's safe.

Ref:
https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClarCAC

lohphat

@jonathanlee There's a great playlist describing QUIC at the protocol level. Even with the AppID details of the protocol details, so much of the payload is encrypted that individual URLs are cloaked so that they can't be detected by filters (pfBlockerNG, snort, suricata) -- you have to block the entire QUIC request or nothing, you can't pick it apart.

HOW QUIC WORKS
https://www.youtube.com/watch?v=HnDsMehSSY4&list=PLW8bTPfXNGdDcSDSmcfYs3ynYOdc1cXSh

JonathanLee

@lohphat

HTTPS 3 uses UDP and TCP over port 443

Current HTTPS uses TCP.

To disable quic you just block UDP traffic to port 443 and port 80.

There is a overview of it with Palo Alto and other firewalls.

Thanks for the reply

You just close off UDP over 443 to stop it. I did and you can see the QUIC error code with Facebook during testing. After it will default back to TCP use and Facebook runs again.

That's the current recommendation. Without 443 UDP access it won't work.

Chrome browser can decrypt it. But yes it is an issue that's why the major firewall companies want it blocked if it's not required.

JonathanLee

@lohphat
https://youtu.be/QRRHA_5hS2c

This is amazing they decypt QUIC in this with pen testing software.

So why isn't SQUID doing this?

lohphat

@jonathanlee I know what QUIC is and how to block it. That's not the issue. I WANT to allow it but from a list of acceptable domains. That's the problem with pfSense, you can't whitelist QUIC by domain easily. That's my ask, It's going to be complicated to scope out what the QUIC request is asking for and then be able to whitelist "trusted" domains (Google, et al).

lohphat

@jonathanlee This works because the TLS 1.3 keys are being captured at the host where the QUIC request is originating from.

A gateway (pfSense, PANs, Cisco, etc.) don't have access to those client keys UNLESS there's a capture agent on each host -- OR all the host keys have some sort of enterprise PKI management in place to escrow client keys on the fly.

This is a hard problem to tackle.

Patch

Perhaps using pfblocker to create and alias native for the ASN then include that in the black or white list for the QUIC rule