Don't count on reliability when amateurs are in charge. Last two days with
SHITOR: connection refused, connection refused, cannot connect cannot
connect.

On Wed, 17 Aug 2022 05:04:38 -0000 (UTC), in article
<XnsAEF6850AD968Fanonymouswwe8sdddddd@46.165.242.91> anonymous
<anonymous@invalid.com> wrote:

> Don't count on reliability when amateurs are in charge. Last two days with
> SHITOR: connection refused, connection refused, cannot connect cannot
> connect.

No problem over here. But you're right, many things can go wrong when
amateurs run the Tor Browser software. Hard to provide support with so
little information.

In article <1d40a319bc9f68bd0e24acaaa1f1618f@msgid.frell.theremailer.net>
Fritz Wuehler <fritz@spamexpire-202208.rodent.frell.theremailer.net> wrote:
>
> On Wed, 17 Aug 2022 05:04:38 -0000 (UTC), in article
> <XnsAEF6850AD968Fanonymouswwe8sdddddd@46.165.242.91> anonymous
> <anonymous@invalid.com> wrote:
>
> > Don't count on reliability when amateurs are in charge. Last two days with
> > SHITOR: connection refused, connection refused, cannot connect cannot
> > connect.
>
> No problem over here. But you're right, many things can go wrong when
> amateurs run the Tor Browser software. Hard to provide support with so
> little information.

The a-hole Anti Tor moron is back.

(Isn't it amazing how the rest of us post O.K.with that "SHITOR"
browser Tor?)

On 8/16/2022 10:04 PM, anonymous wrote:

> Don't count on reliability when amateurs are in charge. Last two days with
> SHITOR: connection refused, connection refused, cannot connect cannot
> connect.

The NSA is blockin' you bro.

No doubt about it.

Fritz Wuehler <fritz@spamexpire-202208.rodent.frell.theremailer.net>
wrote in
news:1d40a319bc9f68bd0e24acaaa1f1618f@msgid.frell.theremailer.net:

> On Wed, 17 Aug 2022 05:04:38 -0000 (UTC), in article
> <XnsAEF6850AD968Fanonymouswwe8sdddddd@46.165.242.91> anonymous
> <anonymous@invalid.com> wrote:
>
>> Don't count on reliability when amateurs are in charge. Last two days
>> with SHITOR: connection refused, connection refused, cannot connect
>> cannot connect.
>
> No problem over here. But you're right, many things can go wrong
> when
> amateurs run the Tor Browser software. Hard to provide support with
> so little information.
>

Gee I didn't think you had to be a professional to use a proxy site like
Tor. Also their bridges do not work either. Maybe it's my isp blocking
tor. Same with every install for the last two years. They don't work
outta the box. I'm not gonna join the list of linux nerd coders to use
Tor. If it doesn't work outta the box, it just doesn't work, unlike all
the other software on my machine. Also their lame method of startup is
slow and lame, requires a long wait and sometimes several tries. Also
I'm not going to disable my FW. Only thing you get is 80 and 443. If you
can't provide service to those ports, I'm not gonna give all the hacker
tor nodes more opportunities to hack my connection.

On 2022-08-21, anonymous <anonymous@invalid.com> wrote:

> Gee I didn't think you had to be a professional to use a proxy site like
> Tor.

One doesn't. You do, apparently, but that's your problem.

> I'm not going to disable my FW. Only thing you get is 80 and 443. If you
> can't provide service to those ports, I'm not gonna give all the hacker
> tor nodes more opportunities to hack my connection.

That's just cargo-culting. You've got no clue and it won't make you any
more "safe".

You don't have to use Tor. Noone's after your frog white arse, anyway.

anonymous <anonymous@invalid.com> wrote:

> I'm not going to disable my FW. Only thing you get is 80 and 443. If you
> can't provide service to those ports, I'm not gonna give all the hacker
> tor nodes more opportunities to hack my connection.

| My firewall only allows a few outgoing ports
|
| If your firewall works by blocking ports, then you can tell Tor to only
| use the ports when you start your Tor Browser. Or you can add the ports
| that your firewall permits by adding "FascistFirewall 1" to your torrc
| configuration file. By default, when you set this Tor assumes that your
| firewall allows only port 80 and port 443 (HTTP and HTTPS respectively).
| You can select a different set of ports with the FirewallPorts torrc
| option. If you want to be more fine-grained with your controls, you can
| also use the ReachableAddresses config options, e.g.:
|
| ReachableDirAddresses *:80
| ReachableORAddresses *:443

<https://support.torproject.org/tbb/tbb-firewall-ports/>

| FascistFirewall 0|1
|
| If 1, Tor will only create outgoing connections to ORs running on ports
| that your firewall allows (defaults to 80 and 443; see FirewallPorts).
| This will allow you to run Tor as a client behind a firewall with
| restrictive policies, but will not allow you to run as a server behind
| such a firewall. If you prefer more fine-grained control, use
| ReachableAddresses instead.
|
| ReachableAddresses IP[/MASK][:PORT]…
|
| A comma-separated list of IP addresses and ports that your firewall
| allows you to connect to. The format is as for the addresses in
| ExitPolicy, except that "accept" is understood unless "reject" is
| explicitly provided. For example, 'ReachableAddresses 99.0.0.0/8, reject
| 18.0.0.0/8:80, accept *:80' means that your firewall allows connections
| to everything inside net 99, rejects port 80 connections to net 18, and
| accepts connections to port 80 otherwise. (Default: 'accept *:*'.)

<https://2019.www.torproject.org/docs/tor-manual.html.en>

BTW, the 'FascistFirewall' option is deprecated and internally converted
to 'ReachableAddresses'. So better use that instead.

Nomen Nescio <nobody@dizum.com> wrote:
>On 2022-08-21, anonymous <anonymous@invalid.com> wrote:
>
>> Gee I didn't think you had to be a professional to use a proxy site like
>> Tor.
>
>One doesn't. You do, apparently, but that's your problem.

He just doesn't get it, and I doubt he ever will.
Speaking of Tor as a 'proxy site' is far off.

In article <5474f612847549b1a02bb731bf0284f8@dizum.com>
Nomen Nescio <nobody@dizum.com> wrote:
>
> Nomen Nescio <nobody@dizum.com> wrote:
> >On 2022-08-21, anonymous <anonymous@invalid.com> wrote:
> >
> >> Gee I didn't think you had to be a professional to use a proxy site like
> >> Tor.
> >
> >One doesn't. You do, apparently, but that's your problem.
>
> He just doesn't get it, and I doubt he ever will.
> Speaking of Tor as a 'proxy site' is far off.

Well, he's half right. Both function at layer 7, and proxies
arguably at layer 4.

The OSI model doesn't "fit" real world Internet networking.

Anonymous <nobody@remailer.paranoici.org> wrote in
news:25e8e301ae3fa0c689d4451953913a5c@remailer.paranoici.org:

> anonymous <anonymous@invalid.com> wrote:
>
>> I'm not going to disable my FW. Only thing you get is 80 and 443. If
>> you can't provide service to those ports, I'm not gonna give all the
>> hacker tor nodes more opportunities to hack my connection.
>
>| My firewall only allows a few outgoing ports
>|
>| If your firewall works by blocking ports, then you can tell Tor to
>| only use the ports when you start your Tor Browser. Or you can add
>| the ports that your firewall permits by adding "FascistFirewall 1" to
>| your torrc configuration file. By default, when you set this Tor
>| assumes that your firewall allows only port 80 and port 443 (HTTP and
>| HTTPS respectively). You can select a different set of ports with the
>| FirewallPorts torrc option. If you want to be more fine-grained with
>| your controls, you can also use the ReachableAddresses config
>| options, e.g.:
>|
>| ReachableDirAddresses *:80
>| ReachableORAddresses *:443
>
> <https://support.torproject.org/tbb/tbb-firewall-ports/>
>
>
>| FascistFirewall 0|1
>|
>| If 1, Tor will only create outgoing connections to ORs running on
>| ports that your firewall allows (defaults to 80 and 443; see
>| FirewallPorts). This will allow you to run Tor as a client behind a
>| firewall with restrictive policies, but will not allow you to run as
>| a server behind such a firewall. If you prefer more fine-grained
>| control, use ReachableAddresses instead.
>|
>| ReachableAddresses IP[/MASK][:PORT]…
>|
>| A comma-separated list of IP addresses and ports that your firewall
>| allows you to connect to. The format is as for the addresses in
>| ExitPolicy, except that "accept" is understood unless "reject" is
>| explicitly provided. For example, 'ReachableAddresses 99.0.0.0/8,
>| reject 18.0.0.0/8:80, accept *:80' means that your firewall allows
>| connections to everything inside net 99, rejects port 80 connections
>| to net 18, and accepts connections to port 80 otherwise. (Default:
>| 'accept *:*'.)
>
> <https://2019.www.torproject.org/docs/tor-manual.html.en>
>
>
> BTW, the 'FascistFirewall' option is deprecated and internally
> converted to 'ReachableAddresses'. So better use that instead.
>

Ok thanks for that reply. I do have p 80 and 443 listed in the tor
browser setting. Someone else here is telling me my ISP is blocking tor
but that cannot be since I can connect to tor directly but the so-called
"bridges" simply do not work.