- tor-relays - lists.torproject.org

Re: [tor-relays] Issues with vidalia-obfsproxy-bridge-bundle-0.2.4.12-alpha-0.3.3-alpha on Windows
by Asa Rossoff 01 Jun '13

01 Jun '13

From: Asa Rossoff [mailto:asa@lovetour.info] Sent: Saturday, June 01, 2013 4:33 AM To: 'tor-talk(a)lists.torproject.org' Cc: 'tor-relays(a)lists.torproject.org' Subject: Issues with vidalia-obfsproxy-bridge-bundle-0.2.4.12-alpha-0.3.3-alpha on Windows [A. R.] . > 5) Sometimes, problem #4 never occurs: Tor simply stops generating log messages and I dissappear from the consensus (onionoo status=down). This also takes some hours. This is the state at this moment as I write this message, and looking at the log, there is nothing unusual reported (level=notice/warning) (if beneficial, I can learn how to have Tor generate a full debug log when run directly without Vidalia). Tor is still functioning as a client -- without log messages to the terminal, at least for a longstanding existing connection. [A. R.] Interesting development just now: I went to the Tor console window that has shown no activity for many hours (andonionoo shows me down). I was about to close it and restsart Tor, but on a whim hit the ESC keep instead. Tor immediatiately came back to life, ebginning with the following message "[warn] Your system clock just jumped 64376 seconds forward; assuming established circuits no longer work." and restested it's OR port (which succeeded quickly). I guess it's working again.. will leave it for now..strange trange strange. I guess I can run it from a batch file that pipes a huge file with ESC's into it.. might keep it alive.. Thanks again if any insights; Asa

1 0

Issues with vidalia-obfsproxy-bridge-bundle-0.2.4.12-alpha-0.3.3-alpha on Windows
by Asa Rossoff 01 Jun '13

01 Jun '13

Dear tor-talk and tor-relays experts: Hi, The solution to my problems is probably obvious: "well, downgrade" (or perhaps, if skilled or daring, try compiling the latest code), however: I'd like to report that the current obfsproxy bridge bundle for Windows seems to be essentially unusable on my system. Windows 7 Ultimate x64, first gen i3/2 core/4 thread mobile system. I think this is the first Windows obfsproxy bridge bundle released. Previously I used the 0.2.4.11 pyobfsproxy browser bundle and simply reconfigured it as a bridge, which seemed to work fine and be very stable. My initial difficulties were all my own: configuration file changes between the two versions and filename changes (pyobfsproxy -> obfsproxy). Solved them, to my knowledge. 1) Then, Tor always crashed on startup, which may have been a timing issue as this was mostly/only observed with Vidalia configured to startup with the system/login. This "fixed itself" (more evidence it may have been a timing issue with differing startup/login timing). However, I think this is a bug, as startup with the system should just work (I had no problems with 0.2.4.11). 2) Then, although Tor didn't crash on startup anymore, there were numerous error messages (unfortunately, I don't recall them) in the Tor log when starting with the system, and I think it was not fully working anyway. 3) Maybe a showstopper: in between 20 minutes and and an hour, Vidalia either lost communication with Tor, or Tor was failing in some way. Vidalia did not know it had lost communication, but there were no more log messages, and all the other information tabs either reported nothing, or in the case of the network map -- mapped nothing but showed some connections. Nothing happened if I tried to terminate connections from the interface. Clicking the "Stop Tor" button and then "Start Tor" resolved the issue -- for 20-60 minutes. My solution: stop using Vidalia, and just run Tor directly. I made a hardlink to the torrc file in Vidalia's appdata folder, from Tor's so they could both find it (there is probably a command-line switch or two I could have used :) -- I didn't check!) 4) Now, things were better. Next problem: periodically, usually after some hours of running fine, the Tor log began showing errors re. the cached-microdescs file. First, a permission/file access error, and then hundreds of other errors related to building the micro descriptor cache would be generated every some minutes. Actually---I also observed this problem the first time, even running under Vidalia, that Tor ran without crashing on startup. My solution attempt: delete the file. It was locked. When I closed Tor --- the lock was released [Tor was tied to the file lock] and I could delete the file. I restarted Tor and it worked fine for some hours before repeating this behavior. Once this happens, my node goes down. I think it has to do more bootstrapping work on restart when this file is lost, if I understand correctly. 5) Sometimes, problem #4 never occurs: Tor simply stops generating log messages and I dissappear from the consensus (onionoo status=down). This also takes some hours. This is the state at this moment as I write this message, and looking at the log, there is nothing unusual reported (level=notice/warning) (if beneficial, I can learn how to have Tor generate a full debug log when run directly without Vidalia). Tor is still functioning as a client -- without log messages to the terminal, at least for a longstanding existing connection. 6-sort of) I'll note in passing---in the off-chance it might be an issue on the Tor end, and in the other off-chance that an issue on "my end" is adding to Tor's instability. I suppose in both cases it might be called a Tor bug if in deed relevant at all, as I would expect Tor to handle it gracefully: I have my OR address specified using a DNS name (a dynamic DNS name). I run a dynamic DNS updater that either polls for changes every 5 minutes, or else Tor does a lookup every 5 minutes, because Tor is reporting IP address changes sometimes as frequently as every 5 minutes, between my real IP (which has not changed) and an IP on an entirely different network owned by an unaffiliated ISP!. This gererates frequent ORPort reachablity tests, which are always done, for some reason, on the correct IP address. The incorrect address has a long tracert to another state before it dwindles off to no-reporting private network routers, and a reverse nslookup indicates it is on a cellular address block. --- I will have to study this issue on my own, most likely (bug in updater, my dynamic dns service, etc. - it may be the last known address on one of the configured interfaces on my coputer - which is down -- for when I use my phone's connection on occasion.) I can simply try returning to my old batch file that worked great as a dynamic ip updater, and can the fancy but possibly buggy executable in the system tray. 7) Minor issue: ORPort reachability tests do not always succeed in the 20 minutes alotted (but I can perform a telnet test from a foreign server to the port and get a connection). The tests are repeated and eventually succeed. On the other hand, sometimes the test succeeds within seconds. I have trouble understanding why they would fail (or why they would take more than 30 seconds) unless it is an issue where other nodes refuse to cooperate in reachability testing or make it a low priority. This is probably not a version-specific issue, but might be a design issue. 8) This issue comes chronologically early in the sequence of problems I experienced: Some controls in the Vidalia 0.2.4.12-0.3.3 Settings dialog that I tried didn't save the values, So I relied on manually editing the config files. -------------- If you've read this far, thanks! I will soon--time permitting--and lacking other advice--try the non-obfsproxy bridge bundle (0.2.4.12-alpha-0.2.21) supplemented with the obfsproxy executable from alpha 0.3.3. If that fails, I will go back to the 0.2.4.11 browser bundle configured as a bridge. When I achieve a stable combination, I might try a tool for installing anything as a service and try to run the Tor executable as a service. Seems like Vidalia should be able to talk to it, but I might have to overcome automatic Vidalia behavior like trying to start Tor itself and exiting if the Tor process is killed, etc. ---------------- There are many great minds here, so if anyone has any pointers or links o a page with the info I need, that would be great. Otherwise, consider this a bug report and let me kow if I can aid in debugging. I want to support the Tor network in such ways as I can. Thanks, Asa

1 0

Re: [tor-relays] [tor-talk] Skype banned tor-nodes?
by Mike Perry 29 May '13

29 May '13

Cross-posting to tor-relays to give everyone the heads up - I just added 33033 to the ReducedExitPolicy page for Skype: https://trac.torproject.org/projects/tor/wiki/doc/ReducedExitPolicy Non-relay related discussion should remove tor-relays from the Cc. James Brown: > Hello, people! > > Because many my contacts continue to use Skype and don't want to use any > nice soft (such as jabber, torchat and etc.) I need to use it too. > For protecting of my location and etc. I use it only through Tor (on VM > working under transparently-torifed user). > Some days ago I would be very, very difficalt to connect to skype > through the Tor-net (earlier it was very easy). > As can I see in my Vidalia, my skype application can make resolving > through tor and can connect to hosts through port 443, but conncetions > with port 33033 cannot establish (I can the the trying to open it and > after it it closed immediatly). > As can I see the skype doesn't work without that connections which now > establishes very rarely. > I have 2 versions: > a) the Skype team ban the Tor-connections to skype (but I can still > connect to skype to ports 443 and I can to browse their web-site and > even log in to it through the Tor without any problems) > or > b) many Tor-exits don't let the above-mentioned port (33033) in their > ExitPolicy. > It is not good from the Skype team if they do the first. > If the second hypothesis is right I ask owners of Exit-nodes, if it > possible, to let that port in their ExitPolicies. Not sure if that's actually the problem, but if the only way you can get to Skype is to use a Bittorrent-supporting exit, it certainly seems like a possibility. Thanks for the heads up James! -- Mike Perry

1 0

obfsproxy on freebsd
by Peter Kasper 28 May '13

28 May '13

hi, i'm trying to run obfsproxy on freebsd 9.1, i have installed packages obfsproxy-0.1.4,1 and tor-devel-0.2.4.12.a log file: May 24 16:36:29.000 [notice] Your OpenSSL version seems to be 0.9.8y. We recommend 1.0.0 or later. May 24 16:36:52.000 [notice] To correct this, use a more recent OpenSSL, built without disabling any secure ciphers or features. May 24 16:36:53.000 [warn] The communication stream of managed proxy '/usr/local/bin/obfsproxy' is 'closed'. Most probably the managed proxy stopped running. This might be a bug of the managed proxy, a bug of Tor, or a misconfiguration. Please enable logging on your managed proxy and check the logs for errors. May 24 16:36:53.000 [notice] Failed to terminate process with PID '12021' ('No such process'). when i start obfsproxy directly, there is only obfs2 protocol 2013-05-25 21:09:51 [notice] Starting (obfsproxy version: 0.1.4 (git-94ebc4c3edf1e3e5)). Usage: obfsproxy [obfsproxy_args] protocol_name [protocol_args] protocol_options protocol_name ... * Available protocols: [dummy] [obfs2] any idea? peter ---------- ZPS 14 za 16,90 EUR - vypredaj internetoveho skladu pokracuje! SUPER AKCIA! Registracia nove .EU domeny len za 1,99 EUR! Najdite si strateny alebo ukradnuty telefon programom Zoner AntiVirus Free pre Android Domeny .SK len za 12.29 EUR Ponuka z vydavatelstva Zoner Press Mam rad Android - klikni tu

2 2

Increasing nofiles when running Tor-Relay in a chroot environment
by Sven Reissmann 28 May '13

28 May '13

Hi, I'm running Tor inside a chroot that I built long ago, using this guide: https://trac.torproject.org/projects/tor/wiki/doc/TorInChroot For some weeks my traffic limitations are gone, so I' d like to increase the allowed traffic on my relay. Problem is, that I also need to increase the maximum number of open file descriptors, tor may use. I did this in the limits.conf configuration file, but it has no effect in the chroot environment. Is anyone running a similar setup or has a hint how it could be solved? Regards, Sven. -- PGP Schluessel : https://0x80.io/files/key.asc Anonyme Antwort: https://privacybox.de/srm.msg

1 0

Several IP address on the same box
by Torry Torah 24 May '13

24 May '13

Hi, I have two network interfaces on my server and thus 2 IP addresses. Since tor uses only a very small fraction of my resources (I'm running a bridge), I was wondering if I could put up two bridges, one on each interface. I didn't find anything in the docs about that. Many thanks, -- Torry

2 1

Is TOR using more than just OrPort and DirPort?
by Daniel Wu 13 May '13

13 May '13

I just started a relay (non-exit node, not running a client myself), on Windows, using the latest Vidalia Relay Bundle. Looks like from the configuration, given that I'm running in relay mode, there should be only two ports used by Tor (OrPort and DirPort), right? However, when I run "netstat -ano", I see that the Tor process is using up a lot more ports. There are these connections, from 127.0.0.1 back to itself. Some sort of internal process used by Tor? Not as concerned about these, since these are internal. But still curious. TCP 127.0.0.1:63417 127.0.0.1:63418 ESTABLISHED TCP 127.0.0.1:63418 127.0.0.1:63417 ESTABLISHED TCP 127.0.0.1:63419 127.0.0.1:63420 ESTABLISHED But then I see connections like these: TCP 192.168.1.202:55049 174.136.105.86:9001 ESTABLISHED TCP 192.168.1.202:56804 37.128.208.46:9002 ESTABLISHED TCP 192.168.1.202:56896 171.25.193.9:80 ESTABLISHED TCP 192.168.1.202:57113 109.232.224.74:9001 ESTABLISHED TCP 192.168.1.202:57206 91.227.249.44:9001 ESTABLISHED TCP 192.168.1.202:57221 67.164.46.197:9001 ESTABLISHED TCP 192.168.1.202:57253 128.31.0.34:9101 ESTABLISHED TCP 192.168.1.202:57259 204.124.83.132:587 ESTABLISHED TCP 192.168.1.202:57260 128.232.18.57:9001 ESTABLISHED TCP 192.168.1.202:57309 204.124.83.131:443 ESTABLISHED TCP 192.168.1.202:57331 81.24.98.236:9001 ESTABLISHED These appear to be the actual Tor relay traffic (192.168.1.202 is my computer). Why are these using ports in the 55000+ range, when I specified my OrPort to be a singular value (in my case, 9031)? I would like to know the port ranges used by Tor for relay traffic, so I can use my dd-wrt to set the QoS by specifying these Tor port ranges. Thanks, DW

4 6

"Localized" TOR exit notices?
by Conrad Hoffmann 06 May '13

06 May '13

Hi all, I recently decided I should run a TOR exit node. I am new to the list and still in the process of setting things up. One thing I noticed is that the TOR exit notice [1] contains a US-specific section (it even says so in the comments). Is there a resource anywhere as to how this paragraph might look in other countries? I am located in Germany for example, and I suppose a short mention of the TMG [2], specifically § 8 and § 15 would be suitable replacement for the above mentioned paragraph. I guess that even if not in the git repo, at least a collection in the wiki might be a neat idea? Or did I just not find it? Cheers and thanks for any hints, Conrad [1] https://gitweb.torproject.org/tor.git/blob/HEAD:/contrib/tor-exit-notice.ht… [2] http://www.gesetze-im-internet.de/tmg/index.html (in german)

2 1

A call to arms for obfuscated bridges
by George Kadianakis 06 May '13

06 May '13

Greetings, A year ago we asked you to run obfuscated bridges to help people in Iran [0]. Many people answered our call and we ended up having a big pool of obfuscated bridges to give to our users. Unfortunately, today, most of those bridges are down, and fresh ones are needed more than ever, since obfuscated bridges are the only way for people to access Tor in some areas of the world (like China, Iran and Syria). On the bright side, Tor's anti-censorship infrastructure has improved, and now you don't have to send the bridge addresses to us; if you run an obfuscated bridge with Tor 0.2.4.x, Tor will send its own address to BridgeDB [1] like normal bridges do. Also, obfsproxy was rewritten in Python and it now supports a new pluggable transport called 'obfs3' which works even in China [2]. We have dropped support for the C-version of Obfsproxy, and the new Pluggable Transport Bundles contain the Python version [3]. Finally, future pluggable transports will be developed for the Python version. Looking into BridgeDB, we have 200 obfs2 bridges, but only 40 obfs3 bridges: this means that we need more people running the new Python obfsproxy! Upgrading obfsproxy should be easy now, since we prepared new instructions and Debian/Ubuntu packages. If you run Debian or Ubuntu check out these instructiosn: https://www.torproject.org/projects/obfsproxy-debian-instructions.html.en otherwise use these: https://www.torproject.org/projects/obfsproxy-instructions.html.en (and make sure your pip is upgraded so that it uses HTTPS [4]) Furthermore, Tor's support assistants need some _unpublished_ bridges to give to censored users who ask for help via email. To configure an unpublished bridge you add "PublishServerDescriptor 0" to its torrc. After you do so, fire up Tor, and check its logs to find the ports that 'obfs2' and 'obfs3' are using. Send your IP and ports to tor-assistants(a)torproject.org. Finally, if in the future we need you to do something extra (for example to upgrade obfsproxy to support a new pluggable transport) we will send another mail to tor-relays. Thanks for the help! [0]: https://lists.torproject.org/pipermail/tor-talk/2012-February/023070.html [1]: https://bridges.torproject.org [2]: In China obfs2 is blocked using active probes: https://trac.torproject.org/projects/tor/ticket/8591 [3]: https://blog.torproject.org/blog/new-name-obfsproxy-tor-browser-bundles [4]: https://groups.google.com/forum/#!msg/python-virtualenv/foXxh-NpdGg/uT0NPc9…

14 26

Support for Relay Operators (signed)
by Moritz Bartl 04 May '13

04 May '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 The last mail was not signed, because the Mail Merge addon does not work together with Enigmail. Sorry. - ---- cut ---- Hi, I just noticed that I never announced that we offer support for relay operators at support [at] torservers [dot] net. You can encrypt your mails using PGP -- https://www.torservers.net/torservers_pub.asc fingerprint B099 CF5D 5B97 DC65 2406 B458 C8F4 2EB2 E033 4E90 Currently, four founding members of Torservers.net read that address. If you are a "Torservers partner", please think about joining the support team. We can use your help! - -- Moritz Bartl https://www.torservers.net/ -----BEGIN PGP SIGNATURE----- iQEcBAEBCgAGBQJRg7atAAoJEOGPxWJITcUAHc4H/2mv6Wlpg5bLA5aHTx7lFn19 Dfgr2NTslfwRSA5CO3HeGRytoEoZUJ1xiZMh3SNZzLB6241WxBhdp5mExXFgTe0e E4WFP9rcDVSY2wuzi9QkjergQy3oeaadL17eiRs//GK+eb9wcBfpZ8OHyCTrauln dTUWVCAdtglptTed4Kx2ZUEPjHVoA9pWr9DQ9mxJjXLbREiu4ru0acC7QYswBj/r zt44LfkqPwEOzCrnvqEKOLT/MPP1lPk27tq7dfsTTozdII7VsrVj+nxdoWsfbFOp MyWe7240q4+0QOxHddWXMAAOgnnHOT+QfMeK1BYc1/FBosm9TAVVQmSQvbsb0HU= =BuJ9 -----END PGP SIGNATURE-----

3 3