| Post Reply | RetroFed Forum Forum Index » Security |
| Author | Message | ||
|---|---|---|---|
davel
lemmy.ml
davel@lemmy.mlJoined: 2023-07-08 |
|
||
| 16 Original | |||
|
HelloRoot
lemy.lol
HelloRoot@lemy.lol Joined: 2025-02-15 |
Aren't all modern browsers already doing DoT or DoH ? |
||
| 2 | |||
davel
lemmy.ml
davel@lemmy.mlJoined: 2023-07-08 |
Even when HTTPS is in place, an attacker can still intercept domain look-up traffic and use DNS cache poisoning to ... Aren't all modern browsers already doing DoT or DoH ?
I think DNS-over-TLS & DNS-over-HTTPS would be no less vulnerable than web-over-TLS & web-over-HTTPS. |
||
| 1 | |||
|
HelloRoot
lemy.lol
HelloRoot@lemy.lol Joined: 2025-02-15 |
I think DNS-over-TLS & DNS-over-HTTPS would be no less vulnerable than web-over-TLS & web-over-HTTPS.
AirSnitch doesn't break TLS/HTTPS at all. Only unencrypted plain DNS traffic is exposed. DoT and DoH are encrypted, so they're fine. |
||
| 1 | |||
davel
lemmy.ml
davel@lemmy.mlJoined: 2023-07-08 |
AirSnitch doesn't break TLS/HTTPS at all. Only unencrypted plain DNS traffic is exposed. DoT and DoH are encrypted, so they're fine.
|
||
| -1 | |||
|
HelloRoot
lemy.lol
HelloRoot@lemy.lol Joined: 2025-02-15 |
Even when HTTPS is in place, an attacker can still intercept domain look-up traffic and use DNS cache poisoning to corrupt tables stored by the target’s operating system. The AirSnitch MitM also puts the attacker in the position to wage attacks against vulnerabilities that may not be patched. Attackers can also see the external IP addresses hosting webpages being visited and often correlate the...
this part has nothing to do with the attack. It was always true. Your ISP or anybody sitting on a network node could do that. Because DNS is not encrypted. It doesn't matter that the rest of the traffic, after the name resolution is HTTPS/TLS. Thats why DoT/DoH was invented. To make DNS queries fully encrypted AND to make them look indistinguishable from normal traffic. So if your system implements it properly, it can not be meaningfully intercepted and used in a poisoning attack. The attack doesn't break HTTPS/TLS cryptography. |
||
| 1 | |||
|
atkdef
lemmy.dbzer0.com
atkdef@lemmy.dbzer0.com Joined: 2024-05-31 |
In my opinion, the whole article is (AI) slop. It says "AirSnitch" but is actually describing "ARP spoofing". Encryption (especially TLS) assumes the underlying transport is insecure. It's called Transport Layer Security, a secure transport made possible by utilising encryption. It already had considered MitM by design. |
||
| 2 | |||
|
Lee
retrolemmy.com
Lee@retrolemmy.com Joined: 2025-07-23 |
Even when HTTPS is in place, an attacker can still intercept domain look-up traffic (DNS) this part has nothing to do with the attack. It was always true. Your ISP or anybody sitting on a network node could do that. Because DNS is not encrypted. It doesn't matter that the rest of the traffic, after the name resolution is HTTPS/TLS. Thats why DoT/DoH was invented. To make DNS queries fully encry...
I'm not disagreeing with anything you're saying and I think the articles about this are sensationalized in the impact in some ways, but I think you're focusing too much on the type of traffic that is typically encrypted with HTTPS/TLS. I think the bigger issue is internal networks where it is still common to run non encrypted and/or unauthenticated services. This is particularly an issue when SSID segreagation (lile guest networks) was used to mitigate this kind of issue. The AirSniff paper shows that SSID isolation in many APs can be bypassed. |
||
| 1 | |||
| Post Reply |
Back to top |