SSL Bug In Firefox 3b5

I’ve encountered this bug I just can’t quite figure out, so I figured I’d put it here. Hopefully with a broader audience someone else had encountered it and perhaps this will lead to the root cause being identified.

For some reason Firefox 3 can’t access Webmin on port 10000, which is how it’s setup on a box I have. It worked in Firefox 2.0, but not 3.0. I’m not sure if it’s something to do with Perl’s Net::SSLeay, which Webmin uses for SSL support, or the port number being 10000. I’ve tinkered a little bit with SSL settings, but so far haven’t been able to figure out exactly what’s going on. It seems to be a regression in NSS.

Anyone notice a regression like this using nightly builds somewhere else? This is the only case I’ve personally experienced it. If you have, then visit bug 423499 and let us know.

Edit [5/4/08 @ 11:30 PM EST]: No idea what’s going on here, but apparently nobody else can reproduce, so calling it quits for now.

5 replies on “SSL Bug In Firefox 3b5”

i have no problems accessing a self-signed certificate on port 10000 (using iis5).

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9pre) Gecko/2008042705 Minefield/3.0pre ID:2008042705

I take it you’ve done the usual thing of creating a fresh profile and trying it. Reason is that my ‘dirty’ profile (from testing various alphas, betas and nightlies of Fx3) wouldn’t recognise EV certificates in Beta 5, until I refreshed it by deleting a number of the files.

I have several FreeBSD and Ubuntu boxes running Webmin on various ports and haven’t had any problems with several different people accessing them all using Firefox 3b5.

Firefox 3 does not allow port 10000 (iy only alows port 80),
In my opinion a good security measure but in some cases like webmin you will need to enable the port

in ff3 type about:config (here be dragons),
add with the values comma seperated eg 10000,10001 (webmin/usermin)

I’d reccomend changing the port first in IE then ebabling the correct ports in ff3 so you don’t have to change it twice.

Leave a Reply

Your email address will not be published. Required fields are marked *