Hi guys, As already discussed bit back on irc chromium has idiotic feature which bans you from connecting to "ports that they deemed unsafe". This creative idea can be overriden with on-launch argument passing where you can tell your explicit port is in reality safe, but still you have to do it prior launching the chromium. Which makes me every time close all the stuff i have open and start over :/ Easiest approach would be just disabling the feature as whole.
I have mixed feelings on this. On the surface, it certainly seems like a stupid feature to me. If I were affected by it, I would probably have patched it out already. Can we dig up some history as to why it was implemented in the first place?
Can't find it, but someone from the herd once showed me the bug.
It probably originates from Firefox, which implemented it as a workaround for a "cross-protocol scripting" vulnerability. http://www-archive.mozilla.org/projects/netlib/PortBanning.html So, unless you know that Chromium has some other safeguard in place for this, I don't think disabling the blacklist entirely would be a good idea. You could always whitelist the ports you need by using the explicitly-allowed-ports command line option in /etc/chromium/default. Just set it and forget it.
Given the date, I guess it was probably first implemented in Mozilla; Firefox did not yet exist.
(In reply to comment #0) > As already discussed bit back on irc chromium has idiotic feature which bans > you from connecting to "ports that they deemed unsafe". This is definitely not something we should do as distro maintainers. And this is just asking for someone calling us idiots for disabling security features (I'm putting aside whether they work, and whether the general security model of the web is broken or not). Feel free to raise that as an upstream issue though. Feel free to contact me (or the herd maintainers) off-bugzilla about this.
