- tor-relays - lists.torproject.org

Make your obfsbridge faster by installing python-gmpy
by George Kadianakis 22 Feb '14

22 Feb '14

Greetings, here is a tip if you are running an obfs3/scramblresuit bridge: If your bridge is feeling too slow or flooded by too many connections, you can help it by installing the python-gmpy package. If you do that, obfsproxy will use python-gmpy opportunistically to perform some crypto operations (modular exponentiations) much much faster. FWIW, in future packages of obfsproxy, the python-gmpy will be installed as a recommended package.

1 0

schedule tor relay uptime/ bandwidth
by Zenaan Harkness 22 Feb '14

22 Feb '14

I know tor relay bandwidth usage per period can be configured, but is it possible to schedule a tor relay to sleep during business hours, and only operate after hours? TIA Zenaan

2 2

Relay unresponsive
by Zenaan Harkness 22 Feb '14

22 Feb '14

Somewhat regularly, I get "relay unresponsive" with a heartbeat delta of about 12seconds. Could this mean my upload pipe is still saturated and I need to throttle back slightly? recent arm log: 13:12:56 [ARM_NOTICE] Relay resumed [6 duplicates hidden] 13:12:31 [ARM_NOTICE] Relay unresponsive (last heartbeat: Sat Feb 22 13:12:20 2014) 12:11:34 [ARM_NOTICE] Relay unresponsive (last heartbeat: Sat Feb 22 12:11:20 2014) 11:10:33 [ARM_NOTICE] Relay unresponsive (last heartbeat: Sat Feb 22 11:10:20 2014) 09:30:24 [NOTICE] Heartbeat: Tor's uptime is 2:18 hours, with 146 circuits open. I've sent 14.23 GB and received 9.69 GB. 09:09:20 [ARM_NOTICE] Relay unresponsive (last heartbeat: Sat Feb 22 09:09:07 2014) 09:08:30 [ARM_NOTICE] Relay unresponsive (last heartbeat: Sat Feb 22 09:08:19 2014) 07:16:39 [NOTICE] Self-testing indicates your DirPort is reachable from the outside. Excellent. 07:12:43 [NOTICE] Performing bandwidth self-test...done. 07:11:31 [NOTICE] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. 07:11:26 [NOTICE] Your IP address seems to have changed to 203.158.36.137. Updating. 07:09:25 [ARM_NOTICE] Relay unresponsive (last heartbeat: Sat Feb 22 07:09:12 2014) 07:08:04 [ARM_NOTICE] Relay unresponsive (last heartbeat: Sat Feb 22 07:07:51 2014) 03:30:24 [NOTICE] Heartbeat: Tor's uptime is 5:52 hours, with 189 circuits open. I've sent 12.95 GB and received 12.78 GB.

1 0

[WARN] Your system clock just jumped 100 seconds forward; assuming established circuits no longer work.
by Zenaan Harkness 22 Feb '14

22 Feb '14

My tor logs (running on Debian) are showing this warning: [WARN] Your system clock just jumped 100 seconds forward; assuming established circuits no longer work. I tried running openntpd as well as ntp packages (debian), and both display the same problem - once or twice a day I get this jump in time of in the order of a couple of minutes. Any idea why? TIA Zenaan

7 18

Multi-instance Tor init script
by Alexander Dietrich 20 Feb '14

20 Feb '14

Hello, the recent thread on this topic prompted me to make a multi-instance init script: https://gist.github.com/7adietri/9122199 It's basically the current official init script and torservers.net's "instances" mechanism frankensteined together. Maybe other people will find it useful too. Config files should be layed out as described on torservers.net: https://www.torservers.net/wiki/setup/server#multiple_tor_processes Best regards, Alexander -- PGP Key: 0xC55A356B | https://dietrich.cx/pgp

1 0

^null$ httpd requests
by phrag 20 Feb '14

20 Feb '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, So I've been receiving a few of these httpd requests on my SSL web server. The webserver runs on the root domain of a subdomain hosting a tor relay. From a whois, i see rgnx is owned by Jacob Appelbaum. The webserver in question is running a good ssl setup according to https://www.ssllabs.com/ssltest/. Any information as to what this could be? ###### ## httpd log ## rgnx.net - - [20/Feb/2014:17:29:46 +0100] "\x16\x03\x01" 301 217 "-" "-" ## logwatch ## Attempts to use known hacks by 1 hosts were logged 62 time(s) from: rgnx.net: 62 Time(s) ^null$ 62 Time(s) A total of 1 sites probed the server rgnx.net A total of 1 possible successful probes were detected (the following URLs contain strings that match one or more of a listing of strings that indicate a possible exploit): null HTTP Response 301 ###### -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlMGPOgACgkQceRvMfxmL+0jMwCgr3zMBm7GngflSXiHB2WzJG/d 7ucAoJDOhmcOeIGUwNZzuaHwTcG/QntN =yDA4 -----END PGP SIGNATURE-----

1 0

Re: [tor-relays] TTTT, multiple runs
by Sebastian Urbach 19 Feb '14

19 Feb '14

Hi Sanjeev, Basically yes. Here are the details: http://web.engr.illinois.edu/~das17/tor-traceroute_v1.html#q-canrunelsewhere Feel free to ask if anything is unclear. -- Mit freundlichen Grüssen / Sincerely yours Sebastian Urbach ---------------------------------------------- Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. ---------------------------------------------- Benjamin Franklin (1706 - 1790), Inventor, journalist, printer, diplomat and statesman On Wed, Feb 19, 2014 at 6:53 PM, Sebastian Urbach <sebastian(a)urbach.org>wrote: > Right now we are at 95 ip's with at least 1 completed run. Hopefully we > can add another 5 to that number and reach the "100 milestone" before the > next data review in 03/2014. Multiple run's from the same ip are very > welcome as well. > Sebastian, Does this have to be run on a Tor Relay? I thought so, for my first run, but re-reading it now I am not sure. If running this on a non-relay would help, I can add a few more servers tonight. -- Sanjeev Gupta +65 98551208 http://www.linkedin.com/in/ghane

1 0

Enable statistics for hardcoded obfsbridges
by George Kadianakis 19 Feb '14

19 Feb '14

Hello people, I'm sending you an email because your bridges are hardcoded in the pluggable transport bundles. We recently added PT-specific metrics in metrics.torproject.org Specificaally, you can see a graph of PT users here: https://metrics.torproject.org/users.html?graph=userstats-bridge-transport If you select the obfs2 transport, you can see that it displays only 300 users, which is not entirely true. We suspect that the reason for the low number of users is because not many bridges are reporting PT statistics to the bridge authorities. This might be for two reasons: a) Your bridge might be configured to be private, that is to not publish its descriptor. This might happen if you have 'PublishServerDescriptor' set to 0 in your torrc. If you have a bridge hardcoded in the bundles, not publishing your descriptor doesn't really provide any security (your bridge is exposed anyway), so you might as well start publishing your descriptor, since this will allow us to gather statistics about the number of users you see. b) Your Tor might not be bleeding edge: Tor only started reporting PT statistics to the auths in tor-0.2.5.1. To upgrade to this version of Tor you can use either the git master or the automated Debian package builds (see https://lists.torproject.org/pipermail/tor-relays/2014-February/003899.html for how to use them). c) You don't have Extended ORPort enabled. With recent versions of Tor, you can enable it by adding 'ExtORPort auto' to your torrc. It would be great if you could fix the above so that your Tor can start submitting statistics! If you have any questions, feel free to ask me!

1 0

Working init script for TOR 2.5.1
by tor＠afo-tm.org 17 Feb '14

17 Feb '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello, i search a working init script for multiple tor instances. I tried it from https://www.torservers.net/misc/config/initd-tor but that is broken. Does somebody have a working one? Thanks for help -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJTASW0AAoJEKawimmefC2InIkP/0guExgToj+B/hk9cQouPNdn J9ml+qdZxeEJH2G8V5NFhre4L1y4lubr9DhvVN0eMQ/vU+Dd/f0KqpO/05DD2pMG z2MJxq5qfvL4M/BApGbsC/+xIZBVRWHNHywO/hlR89sXn1Yd30kbnXYlAIQNCobA 6xsT4zhZ+crhKzUgC6jouIdzq1Wf9nfiChxf4w9UgCbO+t6JTkRBjyX7w0bHcTAP e3hMZBUEiJAuWeB3vubQPiQwvhrqw87yvSj6uNhKAq5u8nWtRo1mStD69jia+bdB yZIKxRgc8Y/+T/Ls8zWDiRvBUdvFd0buVQKiWjn8dX4UNoZNuFGIGtv5U+PfKP+3 osBmf3v20VmkW/7RcC/TAO0/9kqDupkdF4/W9OhzcIKQMv64OwJiEIFjE6mtTM8D sHhRbk++3YsVhSCy504KUvohewltEMpHpGD+/1vDwfebryeelBZTkn6xr51Kk6IM LijzNdcZFwmEtP5NbuioF07NyN5qKMyGUYdUhiDc51BT5ynkis4950lHMgJkpKrO 5ssv1Kw+f3B+53s67LbbaaPwErk1AdxxFnIBZ8RcDMLJIk3BsT/WwujPlF/Ftog1 cc6jLCHcxalMPzBT9b4NbNz9EbpOhqpQE/oUeasBtfPr9606bN2EHSTey4WVcuPp kLPxVVMrvY1B4W4fxI/Q =dy9S -----END PGP SIGNATURE-----

3 4

Tor Relay Downloading much more data than uploading
by borgersnick＠gmail.com 17 Feb '14

17 Feb '14

The log entry is: Heartbeat: Tor's uptime is 23 days 0:00 hours, with 0 circuits open. I've sent 6.83 MB and received 177.12 MB. I don’t think I made any changes to the torrc, intend to provide a relay. I am using trickle to limit bandwidth consumption instead of the built-in method because I didn’t want to learn about the bursting concept. ExecStart = /usr/bin/trickle -d 500 -u 500 -t .5 /usr/bin/tor --runasdaemon 0 --defaults-torrc /usr/share/tor/defaults-torrc -f /etc/tor/torrc --quiet Running on Fedora. Firewall allows external port 80 and 443 access to the server.

1 0