nsSocketTransport.cpp : wrong DNS resolve?

[Calvin Liu]

Hi, all,

Please refer to bug 86917
(http://bugzilla.mozilla.org/show_bug.cgi?id=86917) and 108108
(http://bugzilla.mozilla.org/show_bug.cgi?id=108108).

I found that the call stack like this:

nsSocketTransport::Process
in case eSocketState_WaitDNS
->nsSocketTransport::doResolveHost
*** here we use "mNetAddrList.Init(1);" ***
->nsSocketTransportService::LookupHost (or lookup in cached dns
service)
in case eSocketState_WaitConnect
->nsSocketTransport::doConnection
if failed
->nsSocketTransport::OnConnectionFailed
->mNetAddrList.GetNext(mNetAddress) *** how can we GetNext
here??? ***

Calvin

[Darin Fisher]

if LookupHost is called and returns a result, then it means we already
established a connection to that ip-address and will _always_ use it in
the future when attempting to connect to the given host. this is a
required security feature (unfortunately). if you hit this state then
there are only two ways around it: 1) restart the browser, or 2) toggle
the online/offline switch. yes, neither of these solutions are exactly
userfriendly, but as i said it is a requirement (in order to prevent DNS
spoofing attacks).

darin

[Calvin Liu]

What's "DNS spoofing attack"?

Can you give a brief instruction or some relative links?

Calvin

Darin Fisher <da...@netscape.com> wrote in message >