[Autogenerated] DNA's over https can be
implemented directly on the browser with
just a few settings changes. Gabriella has
volunteered to test it out here. We RBAC a
Gabriella station. She's going to start a
new capture and then flush her DNA's
cache. She'll open up, edges her browser
and then go to www dot Globomantics Docker
back in wire shark we can see that her
DNA's queries are in clear text. There's w
w dot Globomantics dot com. She'll go
ahead and mark the last response to make
it a little easier for us to see when the
next query starts. She opens up Firefox
and goes back to Globomantics dot com.
Notice there's no more DNA's queries.
Wonder where they are. You know, she
cleared her cache at this time. She's used
Firefox and Firefox by default. Uses DNA
Jest over https so she actually sent
that'd Jest request to a Cloudflare
server. But since it was HTTP s, we can't
see it in clear tat. Let's change our
filter for the Cloudflare server so you
can see where she did a query for Mozilla
dot Cloudflare dash d n s dot com to find
that DNA server and then if we put in the
I P addresses for those two servers will
be able to sort of. See that DNS query
there. Now we can actually see the TLS
conversation. There's our client Hello to
the Cloudflare Server, and somewhere in
the encrypted application data is our DNS
query for www dot Globomantics dot com. If
I add into the filter for TLS matches
Pluralsight, I'll be able to tell when
Gabriella went to the do H server, then
see where she went to the Web server that
she requested in the do H query. Now I'm
stuck I can see the TLS conversations, but
I certainly can't read them. Beyond the
TLS handshake itself, all of the data is
going to be encrypted. There are methods
for grabbing the information necessary to
decrypt the TLS, but that's another
course. Now let's switch Gabriella over to
next D N s, which is the other do H server
that supported by Firefox. I'll go into
options and network settings and just
change the provider to next DNA's. She'll
clear her cache will mark the last packet
that was captured, and now we see TLS
conversations going out to firefox dot d n
s dot Next d n s dot io. This time I
changed the filter instead of DNA's
matches to frame matches that way, whether
I see it in DNS or I see it in teal us, I
will get the packet. And there's our new
TLS connection request to Pluralsight dot
com. Now we know how clients get there'd
nested information so we can check that
first if we have any troubles. We also saw
how to clear the cache on the client and
server in case our cache is stale. Then we
set up dough on our client to hide our
browsing habits from our ISP up next, modifying DNA's configuration for servers.