Dns spoofing and ssl site [duplicate]

This question already has an answer here:

Can anybody explain what happens in this situation

Lets assume we hijack dns server and rediret users form goodsite.com to badsite.com and also goodsite.com use ssl so when user redirect to badsite.com the browser shows alarm and users find they are in wrong place but what happens if attacker sign badsite.com by somthing like lets encryp so the browser does not shows alarm and attacker gets result.

May be I did not not explain enough

Imagine I change dns server of some user to mine and add goodsite.com to my server and add ssl to it by lets encrype ( lets encrype doesnt require to prove you are owner of the goodsite.com) so when user want to see goodsite.com they come to my goodsite.com and becuse ssl is verify their brwoser doent complain and they dont find anything wrong.

So the ssl doesnt protect againt dns attack!!!

Continue reading Dns spoofing and ssl site [duplicate]

How does DNSCurve protect against forgery in a man-in-the-middle attack scenario?

This Question is about DNSCurve. I thought of DNSCurve as “HTTPS for DNS” (like in this Answer) but had some resent thoughts about the trust-relationship between resolvers and nameservers serving the public-keys.

Here an example to expla… Continue reading How does DNSCurve protect against forgery in a man-in-the-middle attack scenario?