| Author |
Message |
brookz
New Forum Member


Joined: Jun 08, 2004
Posts: 8
|
I've been doing some ethereal packet sniffing on my Vonage mta while i unplug it and plug it back in..
It looks like each time I do this the box fails authentication once or twice, then it passes authentication the next time it tries. -here is a section of the a packet when it fails
WWW-Authenticate: Digest realm="216.115.25.20", domain="sip:216.115.25.20", nonce="1801737013", algorithm=MD5
-and here is a section of a packet when it passes
Authorization: Digest username="myphone#", realm="216.115.25.20", nonce="1801737013", uri="sip:atlas5.atlas.vonage.net:5061", response="md5 key is in here", algorithm=MD5
Only difference seems to be that when it passes it had an md5 key in there, which i assume is my encrypted password and my phone # as the username... the nonce="1801737013" , does anyone know what that is? it appears in both |
|
|
|
|
 |
RemyJ
Vonage Forum Associate


Joined: Jun 02, 2004
Posts: 13
|
It's all part of the digest authentication mechanism. The first request has to fail. It triggers the server to send the nonce value which the client uses as part of a hash of the userid, password etc. The hash is then returned to the server which does the same hash operation. If the 2 hashs are equal, you're authorized. This way, the password itself isn't sent over the wire. |
|
|
|
|
 |
KrautDog
Vonage Forum Associate


Joined: May 11, 2004
Posts: 17
|
Students at IIT in Chicago recently completed labs with call tracing using Ethereal. The .ppt presentation has a section on the call setup and teardown process. See: http://ewh.ieee.org/r4/chicago/recent.html
Kraut_Dog |
|
|
|
|
 |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum |
All times are GMT - 5 Hours | |