- tor-relays - lists.torproject.org

[WARN] crypto error while checking RSA signature: padding check failed
by Zenaan Harkness 24 Feb '14

24 Feb '14

Occasionally (such as just now) I have seen these two errors in arm: │ 13:21:25 [WARN] crypto error while checking RSA signature: padding check failed (in rsa routines:- │ RSA_EAY_PUBLIC_DECRYPT) │ 13:21:25 [WARN] crypto error while checking RSA signature: block type is not 01 (in rsa routines:- │ RSA_padding_check_PKCS1_type_1) Are they anything to worry about? Zenaan

2 1

ExtORPort notice
by Delton Barnes 24 Feb '14

24 Feb '14

Upon upgrading obfsproxy to 0.2.6 and Tor to 0.2.5.1-alpha-dev (git-f63b394d90583b77+96972c4) for scramblesuit, I got this in the Tor log: Feb 15 04:40:03.000 [notice] We are a bridge with a pluggable transport proxy but the Extended ORPort is disabled. The Extended ORPort helps Tor communicate with the pluggable transport proxy. Please enable it using the ExtORPort torrc option. How should this be set? What does it do? I saw some web pages suggesting "ExtORPort 6699" for statistics-gathering purposes. Thanks, Delton

3 2

TTTT, multiple runs
by Sebastian Urbach 24 Feb '14

24 Feb '14

Dear list members, The "multiple runs" question is now added to the FAQ at the "Trying Trusted Tor Traceroutes" project site. 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. Thank you for your support ! Want to help ? Project site: http://web.engr.illinois.edu/~das17/tor-traceroute_v1.html Want to see the results ?: http://datarepo.cs.illinois.edu/relay_scoreboard.html -- 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

4 3

Obfsproxy help
by I 23 Feb '14

23 Feb '14

3 3

Repeated "failed to get unique circID." in the log
by Patrick ZAJDA 23 Feb '14

23 Feb '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I updated my tor relay to Tor 0.2.5.2-alpha (git-7d29e36edb6d0cf0) yesterday, using Tor repository for Ubuntu. I checked the log, and see the following message repeated again and again: "Feb 20 09:52:38.000 [warn] No unused circ IDs. Failing. Feb 20 09:52:38.000 [warn] failed to get unique circID." In fact, this message is repeated so often that I can not even find the last different message in the log... :) I looked for some informations about this message but I didn't find my answer... I read something about used threads, (NumCpu in torrc) and another about bandwidth, so nothing precise. What does this message means? Thanks, - -- Patrick ZAJDA Skype : gansta93 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTBcTdAAoJEKPVT2DeSPb4ZfkIAKSK5aWvRyBh3uNhWwRegARG QkjoXSgkSBCxQcIFfLPTjBYk+dVNJVTsFvQGstTIQt10/Xu62eMu5DD1yNcAroa7 aFIKHaJkQNwel7j92dyIbZgJ2Vsoe1xIQK2Az3YJGc5S6os116H8dpsmr+jxoH+z Aeh7wneCpiHjXkeD37neXUlbCt4O9WG+Otf5d3gVmJ3eGvixmfY+2KH9WpKs9laA ijt2fu8vwPCseN0spEC9abOo+mLDF0mloxU9w872bhKfig4IpyFt+DqF6VZApUHv Sx6kpN34zFsTzbdzSJovfz6yk6BGekQiMN3v4t30q8c1cfk14EQaFPSdvfIlv3g= =NxPQ -----END PGP SIGNATURE-----

2 1

Tor relay failure
by starwars1070＠gmail.com 23 Feb '14

23 Feb '14

Hello I am experiencing errors I recently upgrade my computer system and os to windows 8.1 pro an now I am having trouble with the tor relay I was running I have configured the firewall and my router to forward traffics to the tor relay port I have centry link for my ISP I am able to establish an or connection to the directly servers but I keep on getting a server error saying your server port can not be connected and now the past three days I have been getting both my or and server port unable to connect to the tor and my relay will not relay traffic

1 0

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