Can't believe that two versions after introducing support for DNS-over-TLS, unbound still makes a new TLS connection (handshake and everything) *for every DNS request*.pic.twitter.com/HzkHXfva2I
This is the legacy version of twitter.com. We will be shutting it down on June 1, 2020. Please switch to a supported browser, or disable the extension which masks your browser. You can see a list of supported browsers in our Help Center.
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Add this Tweet to your website by copying the code below. Learn more
Add this video to your website by copying the code below. Learn more
By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.
| Country | Code | For customers of |
|---|---|---|
| United States | 40404 | (any) |
| Canada | 21212 | (any) |
| United Kingdom | 86444 | Vodafone, Orange, 3, O2 |
| Brazil | 40404 | Nextel, TIM |
| Haiti | 40404 | Digicel, Voila |
| Ireland | 51210 | Vodafone, O2 |
| India | 53000 | Bharti Airtel, Videocon, Reliance |
| Indonesia | 89887 | AXIS, 3, Telkomsel, Indosat, XL Axiata |
| Italy | 4880804 | Wind |
| 3424486444 | Vodafone | |
| » See SMS short codes for other countries | ||
This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.
Hover over the profile pic and click the Following button to unfollow any account.
When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.
The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.
Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.
Get instant insight into what people are talking about now.
Follow more accounts to get instant updates about topics you care about.
See the latest conversations about any topic instantly.
Catch up instantly on the best stories happening as they unfold.
Can't believe that two versions after introducing support for DNS-over-TLS, unbound still makes a new TLS connection (handshake and everything) *for every DNS request*.pic.twitter.com/HzkHXfva2I
I'm convinced that while DNS-over-TLS makes more sense as a protocol than DNS-over-HTTPS (DNS requests are small and have unique IDs), the DNS software ecosystem is just unprepared to handle DoT, while there's solid software to reuse for DoH.
Today my DNS resolver broke, as it does (is it the chroot? the python bindings? the DNSSEC anchor? the DoT proxy? who knows!), so I decided to take another look at connection reuse support, 6 months later. AFAICT, nope. Nothing.
What I _did_ find is that when linked against OpenSSL 1.0.2 (the Homebrew default), Unbound does not check TLS certificates. There's a note in the docs so I guess it's fine. > The cert name match code needs OpenSSL 1.1.0 or later to be enabled. (╯°□°)╯︵ ┻━┻
Everywhere I look in the ecosystem there are C parsers, frustrating UX, suspect OpenSSL bindings, hand-rolled concurrency, bad connection management. Thing is, Go spoiled me. I want to rebuild it all with miekg/dns, some goroutines, net/http and crypto/tls.
(The DNS-over-HTTPS stub part, that is. I am cursed with DNS opinions and there's no chance I'm reimplementing any of the actual cache, hardening, minimisation, prefetching, DNSSEC, and recursion logic. I blame @OGudm.)pic.twitter.com/HcXLjL91Nn
Try dnscrypt-proxy. Written in Go, does connection reuse, padding, cert pinning, caching, filtering, etc.
Wait, this is great.
But hey, are you making releases with Go master to have TLS 1.3 before I'm done testing it? ಠ_ಠ
Helping you test it :)
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.