News for hackers. Stuff that matters.
Re:TurboTLS: TLS connection establishment with 1 less round ... by sam0x17 on Tuesday February 14, 2023 @09:33PM (#34799304)
Having debugged stuff for someone crazy who wanted less than 50ms global latency for a private search engine I can tell you the TLS negotiation adds significant time the first time you initialize the connection
Re:TurboTLS: TLS connection establishment with 1 less round ... by 8n4vidtmkvmk on Wednesday February 15, 2023 @02:56AM (#34801207)
50ms is impossible. Lowerbound is 68. One-way.
Re:TurboTLS: TLS connection establishment with 1 less round ... by sam0x17 on Wednesday February 15, 2023 @02:57PM (#34809720)
emphasis on wanted. And it was quite obtainable depending on geo location. Some locations 70 was best we could do, but most of the US east coast we were able to get around 40
Re:TurboTLS: TLS connection establishment with 1 less round ... by Karrot_Kream on Wednesday February 15, 2023 @03:38AM (#34801440)
I've designed my own private CDN and unless you have edges near each geo, you're not getting that kind of latency. And even after TLS negotiation you have no idea what the MSS on a link along the way will be causing fragmentation and retransmits. I've made do with some shenanigans with Noise and pre shared certs and have tried to make payload sizes as small as possible.
Re:TurboTLS: TLS connection establishment with 1 less round ... by sam0x17 on Wednesday February 15, 2023 @02:58PM (#34809731)
Yes this was using a presence in every GCP and Cloudflare and AWS edge location simultainiously all hooked together with latency based routing
Re:TurboTLS: TLS connection establishment with 1 less round ... by Karrot_Kream on Thursday February 16, 2023 @03:29AM (#34816367)
Hah gotcha. Hope you got paid well for that. I do it for my own pleasure, but it's a lot of work to do as the internet just isn't designed for low latency interconnect.