On 20 Sep 2014, at 17:02, Surf Norway wrote:
I've installed the tor package via homebrew, and cofigured
/usr/local/etc/tor/torrc according to the documentation.
My problem is that every time I try to use launchctl I get an error,
both as an admin user and via sudo.
what OSX version you
I am wondering that another effect of the heartbleed was increased TLS
overhead, that I saw many times also before April-7.
Unfortunately I do not store more than 7 files worth of logs:
Apr 1 02:50:23 localhost Tor[394]: TLS write overhead: 7%
Apr 1 08:51:35 localhost Tor[394]: TLS write
On 13 Feb 2014, at 13:10, Sebastian Urbach wrote:
Dear honorable list members,
Some stats from my side:
bash-3.2$ PPS=200 DONTERASE=yes time ./traceroutes.sh
1645980.86 real 28760.92 user181530.51 sys
Started on 27 Jan 2014 00:49 GMT
Finished on 15 Feb 2014 02:02 GMT
ca. 19
On 23 Jan 2014, at 20:34, Andreas Fritzel wrote:
[...]
Is there anyone who can help me out with this? I was thinking about using
SOCKS, but it didn't work out :(.
how about socat ?
[0] http://www.dest-unreach.org/socat/
Thanks,
-mateusz
signature.asc
Description: Message signed with
On 21 Jan 2014, at 21:57, Anupam Das wrote:
Hi Mateusz,
If there wasn't any network connection then the script would
not give the right traceroutes even though the script will still run (with
empty traceroute results). So if it is not too much of a trouble please
restart
On 22 Jan 2014, at 22:04, Nikita Borisov wrote:
On Wed, Jan 22, 2014 at 4:29 PM, Mateusz Błaszczyk blah...@gmail.com wrote:
Few question Anupam,
1) is that only for relays that are in the relay-ips.txt file, what about
relays setup after?
2) I think I have sent the results for first
On 12 Jan 2014, at 02:57, nano wrote:
I haven't looked into this at all yet, thought I would share it here first.
Both my exit relays [0] received these repeated warnings around the same time
yesterday:
timestamp [warn] Received http status code 404 (Not found) from server
