Version 13 (modified by dj, 6 years ago) (diff)

Report of running a flashproxy

#7425 is the ticket for usability testing.

Problems encountered

ISP blocks outgoing port 25: flashproxy-reg-email fails. Exception message is

socket.error: [Errno 101] Network is unreachable

David: in the log that was sent to me, flashproxy-reg-email took 43 seconds to fail, after which flashproxy-client tried the next registration method. If we can force it to fail within a few seconds, it's fine, as we can fall back to another method, and rendezvous is expected to take tens of seconds.

If you change your remote port away from the default of 9000, you need to edit your torrc in order to change the port number. Vidalia's button to edit the torrc is an almost-reasonable way to do this, but because of #6147 it doesn't currently work.

Can stall at 50% or 85% bootstrapping. This might be related to Tracked by #7733. This may mean that you got only one proxy and you have to restart to try to get more. Link. David: I have seen a stall at 50% for about a minute, during which time Tor sends no traffic, showing the message "no live bridge descriptors" or similar. Then after a while (about a minute) it continues.


bastik: Re-tried on 15th Dec. 2012: Browsing was as "fast" as vanilla Tor can be (or at least I experienced it). Tried debug-mode and saw "flashproxy-reg-email.exe" to be called in intervals, but never noticed any proxy switching process during browsing.

  • Successful, Windows XP (32bit) SP3, freshly unpacked bundle, instantly bootstrapped, browsing was fast. Port-forwarding was not required. Proxy-switching was never noticed.
  • Jon Doe: I tried the Windows 64 bundle (tor-flashproxy-pyobfsproxy-browser-2.4.7-alpha-1-x86_64_en-US.exe), on Windows 7 Home Premium 64 bit SP 1. Following are my experiences:

A.) I edited torrc for non-standard port (not 9000), and I port forwarded in my router. No issues, worked fine when launched.
  B.) I launched vanilla bundle and I didn't forward port 9000, and Tor connected fine.
  C.) Surfing is noticeably slower vs. non-Flash and non-pyObfsproxy TBB bundles.

Antivirus reports

Part of the Windows environment are a zoo of different antivirus tools. The most common of them detected nothing. I checked the new executables on virustotal:

bastik: All "findings" are by the same products and are the same "threat". I don't know what triggers here, but I had this problem with compiled AutoHotkey scripts as all of them contained parts of the same (clean, but abused by malware sometimes) executable. I don't expect many complains from users.

Running a proxy

I've had a flashproxy running for many days in a browser, and it remains mostly idle except for once or twice a day when it attempts to connect to some domestic broadband IP usually in Iran, Syria or China. It never gets through to them (just TCP SYN sent to their port 9000 with no reply). Perhaps we need to somehow improve the instructions on port forwarding. -dj

Finished stuff

Self-extractor appears to work differently than the obfsproxy bundles. Doesn't give you a choice of where to extract, and shows a console window while extracting. Link.
bastik: Because you said obfsproxy bundles here I tried them; they give indeed a choice of where to extract and do not show a console window. David: Fixed in the latest (#7824) bundles.