> That's incredibly niche The very website we're talking about in this submission is specifically made for vintage computers! But I agree, relatively niche. >

> That's incredibly niche The very website we're talking about in this submission is specifically made for vintage computers! But I agree, relatively niche. > Need some secure way to pass around the SHA256 (or whatever) hash you're using for verification. That gets passed out-of-band before actually downloading anything from the registry. In the case of Arch, every package is signed by developer keys that are securely fetched on initial install, and later fetched as a package. Less niche use cases are doing latency sensitive things over HTTP (which overall I wouldn't recommend, but sometimes you're stuck with 3rd party stuff), then adding the handshake can easily double the time for the connection. For example, one website I have can have the TCP connection be established in ~40ms, while the SSL/TLS handshake takes ~100ms. So because of SSL/TLS, the request time more than doubled. If I was serving signed packages over this connection, you can easily skip the handshaking part and when you download thousands of packages, save some time. I don't think that use case is as niche as you think.