Comment by webstrand 4 months ago MitM isn't even necessary, a rogue DHCP server configuring a malicious DNS could attack this. 4 comments webstrand Reply burnt-resistor 4 months ago That's still a MITM, albeit a LAN-local one. Non-LAN WAN isn't the total scope of MITMs. fulafel 4 months ago If my computer asks your computer what dns server to use, and you respond with the address of a nefarious one, it's not necessarily a mitm. webstrand 4 months ago The MitM happens when the client sends packets to the fake IP, I think the argument goes. kortilla 4 months ago That is a form of MiTM. It’s just changing DNS to IP bindings rather than IP to MAC or prefix to ISP.
burnt-resistor 4 months ago That's still a MITM, albeit a LAN-local one. Non-LAN WAN isn't the total scope of MITMs. fulafel 4 months ago If my computer asks your computer what dns server to use, and you respond with the address of a nefarious one, it's not necessarily a mitm. webstrand 4 months ago The MitM happens when the client sends packets to the fake IP, I think the argument goes.
fulafel 4 months ago If my computer asks your computer what dns server to use, and you respond with the address of a nefarious one, it's not necessarily a mitm. webstrand 4 months ago The MitM happens when the client sends packets to the fake IP, I think the argument goes.
webstrand 4 months ago The MitM happens when the client sends packets to the fake IP, I think the argument goes.
kortilla 4 months ago That is a form of MiTM. It’s just changing DNS to IP bindings rather than IP to MAC or prefix to ISP.
That's still a MITM, albeit a LAN-local one. Non-LAN WAN isn't the total scope of MITMs.
If my computer asks your computer what dns server to use, and you respond with the address of a nefarious one, it's not necessarily a mitm.
The MitM happens when the client sends packets to the fake IP, I think the argument goes.
That is a form of MiTM. It’s just changing DNS to IP bindings rather than IP to MAC or prefix to ISP.