Note this doesn't seem to do anything regarding clients
that can generate traffic to find services (hidden), or services
(clearnet or hidden) that can modulate back to find
clients, when combined with a guard (selected by chance
in front of the findee) that is listening for the patterns.
To defeat
Hello,
Can you please log info or debug level and try to connect to a hidden
service that is up and running? If not we should open a ticket on trac.
On Oct 7, 2017 08:43, "Moses" wrote:
Hi,
I can not connect to Tor after upgrading to 0.3.1.7, the bootstaping is
100% completed, but I still can
Add this line tor your torrc file, and restart TorBrowser. "Log debug file
/Users/“your username"/tor.log”
Adapt the directory to your OS's filesystem.
> On Oct 7, 2017, at 9:20 AM, Seby wrote:
>
> nd try to connect to a hidden
> service that is up and running? If not we should open a ticket
Hi,
Strange. Just after I changed the log level to info, it starts working and
I could connect hidden service as before, and I deleted 'log info' in the
torrc file. It remains working. No other settings in the torrc file changed.
On Sat, Oct 7, 2017 at 4:20 PM, Seby wrote:
> Hello,
>
> Can yo
