Joe Abley <[email protected]> wrote:
    > On 20 Oct 2026, at 18:48, Michael Richardson <[email protected]>
    > wrote:

    >> Want Trust? Use DNSSEC.

    > Where do you imagine the validation happening in this scenario?

Ideally, it would be local.

Classic DHCP does not supply a name for DoT to work right, so I think that
without RFC9463, you can't do DoT until you've unblocked the portal to
reach a "public" DoT server.  At which point, a client could allow DNSSEC to
occur there.
(Looking at 9463, I was kinda hoping it offered no DHCPv4 solution)
I *think* that RFC9463 could list this anycast v4, along with a DNS-ID
to validate so that DoT would work.  Or it could just use another IP.

    > What is the expected end-user experience if (shock!) the response to
    > some query is not signed?

Do you mean, what if the portal DNS server lies about all results in order to
get one to visit the portal?   I don't know.  I think that many clients just
allow DNSSEC to be off, and if they would stick with using the captive
browser, and use proper provisioning domains to isolate the caching of the
bogus DNS data...
But, CAPPORT has better tools for doing this, and the client support is
pretty widely available.  When that works, it works great on my laptop, I think.

    >> Want Privacy? Use it to find your DoT host.

    > What is the threat model that is defended against when using DoT with a
    > server that cannot present a certificate you can validate?

I'm saying, you really don't get privacy on that captive network.
You have to unblock it first.  Then, once you have that, you can turn on
whatever privacy tools/VPNs/etc. you have, and then you can do DoT/DoH
over that.  If the captive portal network tries to intercept the DoT/DoH
then a client should NOT proceed.

Again, that's why the captive browser is way smarter.
I'm annoyed with Ubuntu for dropping that, and I would love to find a way to
turn that back on.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     [email protected]  http://www.sandelman.ca/        |   ruby on rails    [
]       My working hours and your working hours may be different.            [
]  Please do not feel obligated to reply outside your normal working hours   [

Attachment: signature.asc
Description: PGP signature

_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to