Hello all,
my current experience of Tor is very frustrating in that it generally
won't work for any length of time without changing identity, sending a
SIGHUP or completely restarting. Since I've tried various versions
(built from source), I assume the problem is with some other OS
component or dep
Just use the TorBrowser Bundle and see if that fixes your issue.
> On Oct 29, 2017, at 6:07 AM, Geoff Down wrote:
>
> Hello all,
> my current experience of Tor is very frustrating in that it generally
> won't work for any length of time without changing identity, sending a
> SIGHUP or completely
Sadly not available for my OS.
On Sun, Oct 29, 2017, at 06:39 PM, Jacki M wrote:
> Just use the TorBrowser Bundle and see if that fixes your issue.
>
--
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailma
What OS are you using?
> On Oct 29, 2017, at 11:43 AM, Geoff Down wrote:
>
> Sadly not available for my OS.
>
>
> On Sun, Oct 29, 2017, at 06:39 PM, Jacki M wrote:
>> Just use the TorBrowser Bundle and see if that fixes your issue.
>>
> --
> tor-talk mailing list - tor-talk@lists.torproject.
Geoff Down:
> Sadly not available for my OS.
>
Troubleshooting a combination of Tor from source + Vidalia (still
maintained?) + some browser on an unknown OS is difficult.
What is your OS and browser?
The route to determining the issue probably comes down to this error:
Oct 29 12:50:06.000 [in
On Sun, Oct 29, 2017 at 06:48:00PM +, George wrote:
> The route to determining the issue probably comes down to this error:
>
> Oct 29 12:50:06.000 [info] onion_skin_ntor_client_handshake(): Invalid
> result from curve25519 handshake: 4
Right. That message comes when you tried to do a circuit
On Sun, Oct 29, 2017, at 06:59 PM, Roger Dingledine wrote:
> On Sun, Oct 29, 2017 at 06:48:00PM +, George wrote:
> > The route to determining the issue probably comes down to this
> > error:> >
> > Oct 29 12:50:06.000 [info] onion_skin_ntor_client_handshake():
> > Invalid> > result from curve2
It is not a good idea to be on such a old version of OS X “security exploits
that have been fixed in newer versions", my advice is to update to macOS 10.13
(17A405) or the latest version and try to see if tor works then.
> On Oct 29, 2017, at 2:43 PM, Geoff Down wrote:
>
>
> On Sun, Oct 29, 2
