Browsing Alternate Ports in Mozilla

(This not exactly a Webware issue, but you may experience this in the course of using Webware.)

On a LAN machine, I set my HTTP server to run on port 79. I could browse it with http://foo:79/ using the lynx, konqueror and opera browsers, but mozilla and galeon gave me this mysterious message:

Access to the port number given has been disabled for security reason.

I posted this to netscape.public.mozilla.general and found out that this behavior is in response to the "cross-protocol scripting" vulnerability described at http://www.kb.cert.org/vuls/id/476267.

I also learned that you can override the banned ports by putting a preference in the all.js script of your mozilla site installation:

pref("network.security.ports.banned.override", "79");

My all.js was found at /usr/lib/mozilla/defaults/pref/all.js. I located it with rpm -q mozilla -l | grep all.js.

Credit: Thanks to the folks at netscape.public.mozilla.general for their help. For details, see the thread starting on 2001-12-26, "Access to the port number given has been disabled for security reasons".

-- ChuckEsterbrook - 27 Dec 2001

Which ports are banned? All below 1024 except 80?