I was trying to browse the web with my morning coffee at my favorite
bagel shop the other day. Apparently it was the first time I had been
there after doing a full update on my laptop FreeBSD install.

The network is unprotected but has a signup screen that you have to hit
before you are let through to the Internet. It's always been a little
hinky for FBSD/Firefox, and at some point I observed the traffic for
a working hit to the logon screen and made a little html file of it
in those cases where Firefox would miss automatically detecting the
sign-on.

Sure enough, firefox missed the portal, but unexpectedly, when I used
the link I had saved for it (which goes to port 10080), I got:

This address is restricted

This address uses a network port which is normally used for
purposes other than Web browsing. Firefox has canceled the
request for your protection.

No option to accept a warning and continue or anything like that.
Of course since I couldn't hit the Internet, I couldn't google a
solution. I finally had to do some ssh to localhost with port mapping.

Once on, I found the preference

network.security.ports.banned.override

easily enough. But *really*!? If my url has a port in it, that's the
port I want to use!

Thanks Mozilla.
--
columbiaclosings.com
What's not in Columbia anymore..

Ted Nolan wrote:

> I found the preference
> network.security.ports.banned.override

That pref doesn't exist by default in my windows firefox, presumably
without any value all ports are fair game? maybe whoever built the
FreeBSD firefox thought it was a good idea?

In article <il0ov2Fj5p0U1@mid.individual.net>,
Andy Burns <usenet@andyburns.uk> wrote:
>Ted Nolan wrote:
>
>> I found the preference
>> network.security.ports.banned.override
>
>That pref doesn't exist by default in my windows firefox, presumably
>without any value all ports are fair game? maybe whoever built the
>FreeBSD firefox thought it was a good idea?
>

No, without the pref unusual ports are banned. You have to create the pref
to open them up. I'm not sure what's on the banned list, but it includes
10080 :-(
--
columbiaclosings.com
What's not in Columbia anymore..

On Sunday, July 11, 2021 at 11:49:58 AM UTC-6, Ted Nolan <tednolan> wrote:

> No, without the pref unusual ports are banned. You have to create the pref
> to open them up. I'm not sure what's on the banned list, but it includes
> 10080 :-(

Probably everything except 80, 8000, and 8080.

John Savard

Quadibloc wrote:

> Ted Nolan wrote:
>
>> without the pref unusual ports are banned. You have to create the pref
>> to open them up. I'm not sure what's on the banned list, but it includes
>> 10080 :-(
>
> Probably everything except 80, 8000, and 8080.

I've used firefox to numerous non-standard ports, never had an issue,
could it be that RFC1818 addrs are excluded from the ban?

Andy Burns wrote:

> could it be that RFC1818 addrs are excluded from the ban?
^^^^^^^
YKWIM

On 7/11/21 1:23 PM, Quadibloc wrote:
> On Sunday, July 11, 2021 at 11:49:58 AM UTC-6, Ted Nolan <tednolan> wrote:
>
>> No, without the pref unusual ports are banned. You have to create the pref
>> to open them up. I'm not sure what's on the banned list, but it includes
>> 10080 :-(
>
> Probably everything except 80, 8000, and 8080.
>
> John Savard
>

The Great Firewall would be built into every browser, if the techlord
weenies could have their way.

I'm so glad the NGO tech wonks do all my thinking for me. Keepin' me
safe! Thanks technocrats!

--
███████████████████████████████████
█░░░░░░░░░░░█░░░░░░░░███░░░░░░░░███
█░░███████░░█░░████░░███░░████░░███ [chan] 711
█░░░░░░░██░░█░░░░██░░███░░░░██░░███ spooky mart
██████░░██░░███░░██░░█████░░██░░███ always open
██████░░██░░███░░██░░█████░░██░░███ stay spooky
██████░░██░░█░░░░██░░░░█░░░░██░░░░█ https://bitmessage.org
██████░░██░░█░░██████░░█░░██████░░█
██████░░░░░░█░░░░░░░░░░█░░░░░░░░░░█
███████████████████████████████████