News for hackers. Stuff that matters.
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by bauruine on Wednesday July 16, 2025 @01:34AM (#44579017)
How does DoH work? Somehow you need to know the IP of cloudflare-dns.com first. Maybe your router uses 1.1.1.1 for this.
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by stingraycharles on Wednesday July 16, 2025 @03:55AM (#44579777)
Yeah I don’t understand this part either, maybe it’s supposed to be bootstrapped using your ISP’s DNS server?
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by tom1337 on Wednesday July 16, 2025 @04:02AM (#44579814)
Pretty much that. You set up a bootstrap DNS server (could be your ISPs or any other server) which then resolves the IP of the DoH server which then can be used for all future requests.
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by stavros on Wednesday July 16, 2025 @02:45AM (#44579397)
Are we meant to use a domain? I've always just used the IP.
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by landgenoot on Wednesday July 16, 2025 @04:05AM (#44579831)
You need a domain in order to get the s in https to work
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by bigiain on Wednesday July 16, 2025 @04:16AM (#44579886)
That's not correct.

LetEncrypt are trialling ip address https/TLS certificates right now:

https://letsencrypt.org/2025/07/01/issuing-our-first-ip-addr...

They say:

"In principle, there’s no reason that a certificate couldn’t be issued for an IP address rather than a domain name, and in fact the technical and policy standards for certificates have always allowed this, with a handful of certificate authorities offering this service on a small scale."

Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by noduerme on Wednesday July 16, 2025 @04:33AM (#44579992)
right, this was announced about two weeks ago to some fanfare. So in principle there was no reason not to do it two decades ago? It would've been nice back then. I never heard of any certificate authority offering that.
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by fs111 on Wednesday July 16, 2025 @08:10AM (#44581321)
> I never heard of any certificate authority offering that.

DigiCert does. That is where 1.1.1.1 and 9.9.9.9 get their valid certificates from

Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by crabique on Wednesday July 16, 2025 @10:24AM (#44582720)
Most CAs offer them, the only requirement is that it's at least an OV (not DV) level cert, and the subject organization proves it owns the IP address.
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by bombcar on Wednesday July 16, 2025 @08:03AM (#44581265)
It the beginning of HTTPS you were supposed to look for the padlock to prove if was a safe site. Scammers wouldn’t take the time and money to get a cert, after all!

So certs were often tied with identity which an IP really isn’t so few providers offered them.

Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by kbolino on Wednesday July 16, 2025 @11:51AM (#44583639)
An IP is about as much of an identity as a domain is.

There are two main reasons IP certificates were not widely used in the past:

- Before the SAN extension, there was just the CN, and there's only one CN per certificate. It would generally be a waste to set your only CN to a single IP address (or spend more money on more certs and the infrastructure to maintain them). A domain can resolve to multiple IPs, which can also be changed over time; users usually want to go to e.g. microsoft.com, not whatever IP that currently resolves to. We've had SANs for awhile now, so this limitation is gone.

- Domain validation (serve this random DNS record) involves ordinary forward-lookup records under your domain. Trying to validate IP addresses over DNS would involve adding records to the reverse-lookup in-addr.arpa domain which varies in difficulty from annoying (you work for a large org that owns its own /8, /16, or /24) to impossible (you lease out a small number of unrelated IPs from a bottom-dollar ISP). IP addresses are much more doable now thanks to HTTP validation (serve this random page on port 80), but that was an unnecessary/unsupported modality before.

Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by yread on Wednesday July 16, 2025 @04:11AM (#44579859)
what about certificate for IP address?
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by landgenoot on Wednesday July 16, 2025 @04:24AM (#44579942)
What about a route that gets hijacked? There is no HSTS for IP addresses.
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by sathackr on Wednesday July 16, 2025 @05:49AM (#44580438)
Presumably the route hijacker wouldn't have a valid private key for the certificate so they wouldn't pass validation
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by federiconafria on Wednesday July 16, 2025 @04:08AM (#44579847)
What about a reverse DNS lookup?
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by maxloh on Wednesday July 16, 2025 @04:43AM (#44580061)
Nope. That is not correct. https://1.1.1.1/dns-query is a perfectly valid DoH resolver address I've been using for months.

Your operating system can validate the IP address of the DNS response by using the Subject Alternative Name (SAN) field within the CA certificate presented by the DoH server: https://g.co/gemini/share/40af4514cb6e

Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by ta1243 on Wednesday July 16, 2025 @02:23AM (#44579267)
And even if you have already resolved it the TTL is only 5 minutes
[dead]
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by k1t on Wednesday July 16, 2025 @02:35AM (#44579331)
Smells like AI and completely fails to answer the question.

How is the IP address of the DoH server obtained?

Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by MayeulC on Wednesday July 16, 2025 @02:51AM (#44579439)
Firefox accepts a bootstrap IP, or uses the system resolver:

> network.trr.bootstrapAddress

> (default: none) by setting this field to the IP address of the host name used in "network.trr.uri", you can bypass using the system native resolver for it. Use this to get the IPs of the cloudflare server: https://dns.google/query?name=mozilla.cloudflare-dns.com

> Starting with Firefox 74 setting the bootstrap address is no longer required in mode 3. Firefox will attempt to use regular DNS in order to get the IP address of the trusted resolver. However, if DNS resolution of the resolver domain fails, setting the bootstrap address is again necessary.

Source: https://wiki.mozilla.org/Trusted_Recursive_Resolver

Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by maxloh on Wednesday July 16, 2025 @04:29AM (#44579976)
Yeah, your operating system will first need to resolve cloudflare-dns.com. This initial resolution will likely occur unencrypted via the network's default DNS. Only then will your system query the resolved address for its DoH requests.

Note that this introduces one query overhead per DNS request if the previous cache has expired. For this reason, I've been using https://1.1.1.1/dns-query instead.

In theory, this should eliminate that overhead. Your operating system can validate the IP address of the DNS response by using the Subject Alternative Name (SAN) field within the CA certificate presented by the DoH server: https://g.co/gemini/share/40af4514cb6e