Hello,

   I'm working at Colubris Networks Inc. and we're building wireless 
802.11b access point bridge/router.  The device is configurable through 
the web and use SSL.  We've tested many browsers and at the moment 
Mozilla is the only one we can't use to configure the product.  Other 
browser that have been tested are IE (Windows/Mac), Opera, Netscape 
4.75, Netscape 6.

   I'm no expert with SSL and therefore I'm not impliyng that there's a 
bug with Mozilla.  I am looking for advice and tips on finding how I can 
resolve that issue.

   Here's the way that our web server and configuration module handle 
the SSL session in hope that one may find a better way or help me out.

   When the user point his browser on our product's IP address, his IP 
is stored and a login page is presented, the user enter his 
authentication information and we validate them, upon successful 
authentication the SSL Session ID and source IP address of the 
authentication is stored and verified constantly.  If one or the other 
(IP or SSL ID) changes we drop access to the configuration pages.

   The problem seems that Mozilla's SSL change the SSL ID each time it 
ask for a configuration page.  I'm assuming that as the IP doesn't 
change.  Is this normal that the session ID for an SSL session change 
each time a new web page is loaded?  Our code seems to work fine with 
other browser.  The reason we're looking at the SSL Session ID is to 
remove the possibility that another PC using the same IP address 
connects to the product and try to change the configuration (while a 
session was opened with that IP address).

Yannick Koehler

NOTE: If you feel more confortable sending me a direct email please do so.


Reply via email to