News for hackers. Stuff that matters.
Re:The Status of HTTP/3 by axaxs on Monday January 13, 2020 @03:23PM (#22038198)
I hate to be a curmudgeon, but I can't help but think that designing a new service over UDP isn't the best idea. DNS has been fighting off wave after wave of attack vectors, some that realistically cannot even be fixed. Making it immune to these vectors is going to look a lot like a slapped together TCP over UDP...
Re:The Status of HTTP/3 by rstuart4133 on Monday January 27, 2020 @04:36AM (#22157995)
> DNS has been fighting off wave after wave of attack vectors, some that realistically cannot even be fixed. Making it immune to these vectors is going to look a lot like a slapped together TCP over UDP...

Unlikely, since TCP + TLS implemented over UDP is a better description of QUIC.

Neither TCP nor UDP were designed when you had to assume the internet to be a battle ground which pitted hackers, police forces, nation states against each other, and you. In such an environment it's not at all surprising to hear Comcast was attacking their own customers using bit torrent or competing video streaming by sending them fake TCP RESETS.

But TLS on the other hand - that's exactly the environment TLS is designed for. They are not going to find it so each to screw with QUIC, because TLS is baked into its DNA.

Re:The Status of HTTP/3 by zamadatix on Monday January 13, 2020 @03:53PM (#22038448)
It is slapped together TCP over UDP. They would rather have made it over IP but protocol ossification has made that impossible.

Don't think of it being UDP as anything more than "it happens to go through existing infrastructure without any or much work"

Re:The Status of HTTP/3 by nikeee on Monday January 13, 2020 @04:38PM (#22038945)
It's fun to see how we kind of reinvented goold old DNS as soon as we use HTTP/3 for DoH. It runs on UDP, but with HTTP in between (and encrypted, of course). We could have done that with DNS itself, but somehow this never gained traction.
Re:The Status of HTTP/3 by zamadatix on Monday January 13, 2020 @11:53PM (#22041961)
The difference DoH started with something nearly every network was guaranteed to have allowed: HTTPS traffic on TCP 443. Trying to wait for every network to allow DNS on 31218 or whatever wouldn't have worked. Even with a massive amount of the web guaranteed to move to HTTP/3 there will be places that still don't allow UDP 443 five years from now.

If ever something seems dumb in network protocol design the answer probably lies with ossification. Hopefully the design of HTTP/3 ends that.

Re:The Status of HTTP/3 by gsich on Tuesday January 14, 2020 @02:35AM (#22042662)
You don't need to wait. Just offer your service on that port and you are done. Why build protocols with shitty networks or shitty admins in mind?

You can use most ports just fine. Multiplayer games show this every day. If those don't work in corporate networks (I include "public" wlan in this) that's fine too. It's not up to you what should be allowed or not in a company setting. ISPs don't block ports just for fun.

And if you are big enough like Google or Facebook, just offer a service only on that port. If it doesn't work, show a warning that the customer should complain to the network owner.

Re:The Status of HTTP/3 by baby on Monday January 13, 2020 @05:30PM (#22039464)
It is basically TCP 2.0 implemented on top of UDP. What concerns do you have with this?
Re:The Status of HTTP/3 by axaxs on Monday January 13, 2020 @05:50PM (#22039627)
Well, I have a lot, but I don't want this to turn into a dissertation about why I don't like UDP for most things.

The biggest red flag to me is that it is trivial to make the server send sizable packets to clients who didn't ask for them nor want them. Spoofing is not a solved problem, no matter how many times people scream at providers to block it before it gets out. Why isn't there a minimal ACK process up front? I mean, this thing is designed such that it's vulnerable to reflection attacks on -day 1-.

Re:The Status of HTTP/3 by baby on Monday January 13, 2020 @06:11PM (#22039800)
UDP is a 4-page RFC that is pretty much a definition of IP with ports. You can easily imagine TCP as a bunch of algorithms on top of UDP. Knowing that I’m not sure what you don’t like about UDP?

Amplification attacks and spoofing are taken care of by QUIC, so these are not problems at the moment.

Re:The Status of HTTP/3 by silisili on Monday January 13, 2020 @06:26PM (#22039942)
That's a little unfair. When someone tells you something relies on UDP, nobody in their right mind assumes that this person implemented TCP features on top. UDP is simple and quick, and the assumption is that there was a reason they chose that route.

AFAICT, QUIC loosely defines a way to do client address validation, but it isn't required! It's worded as 'CAN' and 'MAY' in places, and places outside the spec basically hint that 'oh no! it adds another round trip'. This makes it feel totally bolted on. Why wasn't it required up front? If someone came up to me with this idea of QUIC, the -first- thing I'd tell them is to solve this problem definitively first. The idea seems sound to me, but not if you let everyone turn it off...

Re:The Status of HTTP/3 by magicalhippo on Monday January 13, 2020 @07:38PM (#22040518)
> When someone tells you something relies on UDP, nobody in their right mind assumes that this person implemented TCP features on top.

AFAIK it's rather common in multiplayer games to do TCP-like features over UDP, as they usually need the UDP features but also need reliable transport for some data, and it's rather tricky to do both UDP and TCP at the same time.

See for example https://fabiensanglard.net/quakeSource/quakeSourceNetWork.ph... or https://gafferongames.com/post/reliability_ordering_and_cong...

Re:The Status of HTTP/3 by taf2 on Monday January 13, 2020 @07:54PM (#22040642)
Isn’t the DNS issue unrelated to the protocol of UDP vs TCP but rather how DNS service communicate with each other... triggers an amplification of one request into 100s or maybe 1000s... not really a tcp vs udp issue?
Re:The Status of HTTP/3 by axaxs on Monday January 13, 2020 @08:13PM (#22040764)
There's two issues at play there. What you're talking about is called amplification. That means you get responses far larger than the query. So you send a small query for say, TXT, and the server may reply with KBs of TXT records.

However, that isn't useful by itself. Where it's useful is for attacking a third party. To do this, you spoof the source IP of your query to be the IP of the victim. This is called reflection. See, in TCP, every connection starts with a tiny three way handshake. So if you spoof the IP, the target would just get an unknown SYNACK which is tiny. It wouldn't respond, and nothing further happens. In UDP, there is no such handshake. So the target gets the entire response.

So in short, DNS amplification attacks are only useful with reflection, which doesn't work over TCP.

Re:The Status of HTTP/3 by srj on Monday January 13, 2020 @11:08PM (#22041774)
QUIC addresses this, like TCP it's a connection based protocol. It's just implemented in user space on top of UDP. The server response is required to be smaller than the client hello.
Re:The Status of HTTP/3 by tialaramex on Monday January 13, 2020 @10:58PM (#22041725)
QUIC has address validation, basically if you talk back and forth with a remote party you can get yourself a token which proves you're on path (you might really be 10.20.30.40 we can't tell, but we can tell you can intercept packets for 10.20.30.40 because you received this token we sent there, maybe you're an adversary at their ISP) and you can use that token in future to prove you're still on path for 10.20.30.40, which an off-path attacker wouldn't be able to do because they can't get that token.

So this lets you prevent amplification. If somebody asks a question with a long answer, but doesn't provide the token to prove they're on path, you make them go around again first, a legitimate user sees one round trip wasted to get a token but attacks don't work..

Re:The Status of HTTP/3 by axaxs on Monday January 13, 2020 @11:19PM (#22041817)
I was specifically answering the user's question regarding DNS attacks.

Address validation in QUIC is optional, per the RFC.

Re:The Status of HTTP/3 by manigandham on Monday January 13, 2020 @04:50PM (#22039085)
Too bad no major internet company wants to implement a new version of TCP. We can’t even get IPv6 done after 15 years.
Re:The Status of HTTP/3 by jiggawatts on Monday January 13, 2020 @08:15PM (#22040780)
It's a common misconception that routers handle TCP. They strictly handle only the IP headers (and lower-level headers).

The TCP protocol is implemented only by endpoints, at least in principle.

It's the "security appliances", also known as "middleboxes" that are the problem. Think web proxies, antimalware scanners, firewalls, and inline IDS systems.

These things are the bane of the Internet, because they ossify protocols, blocking any further development.

Re:The Status of HTTP/3 by detaro on Monday January 13, 2020 @08:18PM (#22040810)
Although what a consumer considers a "router" is actually a middlebox doing a bunch of things and does care. (CG-NAT in provider networks is probably another example of a common problematic middlebox)
Re:The Status of HTTP/3 by comex on Monday January 13, 2020 @07:54PM (#22040640)
“A new version of TCP” is pretty much what QUIC (basis of HTTP/3) is. It’s just tunneled over UDP because existing Internet infrastructure likes to drop anything that’s not TCP or UDP.
Re:The Status of HTTP/3 by manigandham on Tuesday January 14, 2020 @12:06AM (#22042014)
That's the problem being cited. The best option is to do a real update of TCP at layer 4, but nobody wants to put in the work and investment to do so.
Re:The Status of HTTP/3 by comex on Tuesday January 14, 2020 @04:12AM (#22043100)
Depends what you mean by "real". You may know this already, but the only difference between UDP and raw IP is the UDP header, consisting of 4 fields in 8 bytes: source port, destination port, length, and checksum. That's it; there's no other protocol overhead. Thus, from a pure technical perspective there would be basically no advantage to running QUIC directly over IP instead of over UDP. The only advantage is from a human perspective, that it's a little more elegant to put QUIC on the same layer as TCP.

In exchange... among other things, it would break all existing NAT implementations, since NAT is based on port numbers and existing devices wouldn't know where to find the port number in the new protocol. So everyone behind a home router would be unable to use the new protocol until they upgraded their router firmware – which of course most 'normal people' never do, so realistically you're waiting years until they get a new router.

Not only is that a gigantic practical disadvantage, it also feels rather inelegant itself. After all, routers shouldn't need to know the details of the transport protocol just to route packets. If it weren't for NAT they wouldn't have to, which is probably why port numbers aren't part of IP itself. NAT sucks. But NAT isn't going away; even on IPv6 some people insist on using it. By tunneling QUIC inside UDP, we at least regain the elegance of separating what routers need to know (IP + UDP) from the real "transport protocol" (QUIC).

Re:The Status of HTTP/3 by detaro on Tuesday January 14, 2020 @12:09AM (#22042031)
Except we already have those layer 4 replacements (i.e. SCTP covers a lot of the same ground), and they've never managed to get out of the niches they are in. How would you suggest "a major internet company" motivate their support better?
Re:The Status of HTTP/3 by kazen44 on Monday January 13, 2020 @05:03PM (#22039228)
implementing a new version of TCP would be nearly impossible because of all the equipment out in the field already.

Changing transport protocol is far harder then changing IP protocol or layer 2 medium.

Re:The Status of HTTP/3 by manigandham on Monday January 13, 2020 @05:32PM (#22039487)
Why doesn't the IP protocol require new hardware if it's a lower layer?
Re:The Status of HTTP/3 by tus88 on Monday January 13, 2020 @07:26PM (#22040414)
It is about the same. It is called TCP/IP for a reason. Although there are more devices that deal with TCP/IP together than just IP alone. Either way it ain't going to happen.
Re:The Status of HTTP/3 by watersb on Monday January 13, 2020 @05:42PM (#22039571)
IP doesn't require new hardware because it's a lower layer.

Transmission Control Protocol - TCP - is baked into the firmware of every client network interface card, and I would suppose in almost all of the switches and routers of business infrastructure.

I have no idea what data centers use. Infiniband and similar things aren't TCP, I think.

Re:The Status of HTTP/3 by lizknope on Monday January 13, 2020 @06:27PM (#22039951)
Infiniband is a lower level than TCP. Infiniband is often used as a replacement for ethernet in a supercomputing cluster.

If you wish you can run IP over Infiniband (IPoIB) but I think most people using Infiniband are running a lower latency protocol like RDMA

https://wiki.archlinux.org/index.php/InfiniBand#TCP/IP_(IPoI...

Re:The Status of HTTP/3 by manigandham on Monday January 13, 2020 @07:05PM (#22040239)
Is IP not handled by network devices and firmware? If it's just software then why don't we have IPv6 everywhere already?
Re:The Status of HTTP/3 by watersb on Tuesday January 14, 2020 @12:53AM (#22042219)
Jiggawatts' comment [0] reminds me that transit routers don't do transmission control.

[0]: https://news.ycombinator.com/item?id=22040780

I enjoy discovering my misconceptions on this topic, as I am no longer building computer networks. Mostly harmless.

Re:The Status of HTTP/3 by john37386 on Monday January 13, 2020 @03:40PM (#22038326)
Totally agree with you. Many big corporations totally block UDP at ISP level because there is no easy/magic solutions against amplified DDoS. They usually use some internal backend for DNS, Ntp, routed through other ISP.

I am afraid that businesses that will host HTTP/3 will be less secure in terms of availavility.

Re:The Status of HTTP/3 by profmonocle on Monday January 13, 2020 @05:56PM (#22039675)
> I am afraid that businesses that will host HTTP/3 will be less secure in terms of availavility.

Presumably most HTTP/3 implementations will gracefully fall back to HTTP/2 (or 1.1) if UDP is filtered. Chrome's existing QUIC implementation already does this.

Every Google property has had QUIC enabled for quite a while now (at least 4-5 years), so if UDP blocking would cause availability issues, affected businesses would've noticed by now.

Re:The Status of HTTP/3 by wahern on Monday January 13, 2020 @07:10PM (#22040283)
In 2017 Google reported that "4.4% of clients are unable to use QUIC". See sec. 7.2 of https://static.googleusercontent.com/media/research.google.c....
Re:The Status of HTTP/3 by profmonocle on Monday January 13, 2020 @10:39PM (#22041624)
Sure, but that doesn't mean those clients are unable to connect to QUIC-enabled domains. Chrome detects that the UDP packets are being lost, disables QUIC, and falls back to HTTP/2.
Re:The Status of HTTP/3 by tracker1 on Monday January 13, 2020 @06:18PM (#22039857)
Many corporations also block SMTP and inbound host ports... doesn't mean the protocol is bad. Hell, many corporations install horrible proxy servers and require all outbound connections go through that proxy.
Re:The Status of HTTP/3 by microcolonel on Monday January 13, 2020 @04:34PM (#22038899)
The fact that many corps block UDP doesn't have anything to do with the necessity of QUIC. QUIC is on top of UDP because we tried with SCTP, but is never coming.

For people who have reasonably configured UDP, it offers a benefit; the fact that some people have broken UDP is neither here nor there. HTTP/2 continues to be an option for TCP-only networks.

Re:The Status of HTTP/3 by throw0101a on Tuesday January 14, 2020 @10:13AM (#22045414)
> I hate to be a curmudgeon, but I can't help but think that designing a new service over UDP isn't the best idea.

They tried with SCTP and DCCP.

Re:The Status of HTTP/3 by faeyanpiraat on Monday January 13, 2020 @03:35PM (#22038281)
curmudgeon (noun): a bad-tempered person, especially an old one.
Re:The Status of HTTP/3 by paulddraper on Monday January 13, 2020 @04:44PM (#22039011)
Forget the narrow waist of the internet; this is the spaghetti ball of the internet.

It violates all of the encapsulation and decoupling principles you learned about as a CS undergrad.

If you have a better transport layer, fine. Make a better transport layer. But rolling the whole thing is the best way to ensure nothing will ever get done.

HTTP/3 is the new IPv6.

Re:The Status of HTTP/3 by yzmtf2008 on Monday January 13, 2020 @05:21PM (#22039376)
> It violates all of the encapsulation and decoupling principles you learned about as a CS undergrad.

I mean, it's not like encapsulation and decoupling ever worked with the networking stack. For example, let's pause a minute and think about which layer does TLS or NAT sit in.

To quote @tptacek[0]: There is no such thing as a layering violation. You should be immediately suspicious of anyone who claims that there are such things.

> HTTP/3 is the new IPv6.

Funny you mentioned IPv6. The famous article [The world in which IPv6 was a good design][1] actually gives some good context on why QUIC is needed, and believe it or not, layering violation was explicitly mentioned.

[0]: https://news.ycombinator.com/item?id=4556125

[1]: https://apenwarr.ca/log/20170810

Re:The Status of HTTP/3 by paulddraper on Monday January 13, 2020 @06:31PM (#22039983)
> which layer does TLS

Transport Layer Security? Transport layer.

> which layer does NAT

Network Address Translation? Network layer.

---

That said, the names aren't as important as the layer and independence. E.g. TLS can be used to secure any TCP traffic: STMP, HTTP, etc.

Re:The Status of HTTP/3 by yzmtf2008 on Monday January 13, 2020 @06:44PM (#22040070)
Some might argue that TLS is on Layer 6, 7 and 4 at the same time: https://security.stackexchange.com/a/93338

Same for NAT: https://networkengineering.stackexchange.com/questions/3145/...

> the names aren't as important as the layer and independence

That's the point. Layers don't mean anything in the real world where ossifications are a thing and replacing infrastructures has a cost. There are plenty of protocols that require cross-layer coupling (aka "layering violations") and asking for layering compliance really doesn't make anyone except layering lawyers' life better.

Re:The Status of HTTP/3 by paulddraper on Monday January 13, 2020 @06:50PM (#22040128)
I didn't say "layers don't mean anything." I said names don't mean anything, especially the OSI layers which as your post points out never really became a thing.

TLS is a encryption layer that works with many protocols. Assigning some special number to it isn't the important part.

Re:The Status of HTTP/3 by yzmtf2008 on Monday January 13, 2020 @06:55PM (#22040167)
> TLS is a encryption layer that works with many protocols. Assigning some special number to it isn't the important part.

Yeah but the point is TLS also doesn't work by just magically changing TCP to TLS (where would you even change that?). It works by using HTTP over TLS. The issue is also not with OSI layers, but the fact that there are dependencies between different components that are supposed to be encapsulated from each other. In this view, HTTPS (HTTP + TLS) isn't really different from HTTP/3 (HTTPS + QUIC).