- tor-dev - lists.torproject.org

torsocks release pending: towards a release candidate
by Jacob Appelbaum 27 Jan '13

27 Jan '13

Hi, Nick and I have been working on a torsocks release. At this point, I think we're at the point where we want to declare a release candidate which if it has no blockers, we'll likely call it a release. I think we'll call it version 1.3 as that seems to have been the intended version. Here is the git repo for all pending changes: https://gitweb.torproject.org/torsocks.git/shortlog/refs/heads/pending-chan… I'll likely merge this pending-changes branch into master in the next day or three. I've gone through all of the torsocks bugs on the Google code site and closed them out. The few that were sorta valid I've decided to close as unsupported as they were either 0) working for some or 1) totally obscure use cases that we never explicitly wanted to support. I think this also includes all of the pending Debian fixes and thus Debian can use our mainline release without patches after the next release. If anyone is horrified, wants to suggest other patches for inclusion, or has anything else to say (related to Torsocks) please speak up! All the best, Jacob

4 7

On Controller, Tor process structure, client software
by Sebastian G. <bastik.tor> 26 Jan '13

26 Jan '13

Hi, This should be just input, nothing too serious. I'm not interested in any kind of feedback. It's probably not worth it. Feel free to use this thread to refer to changes. I'm also not interested in discussions involving me. Feel free do discuss this anyway. It has to be more detailed and the controller itself has to be more modular as well. I hope the attached txt file came through and looks like it should, where it would not look great when dumped into this message. Good Luck. Regards, Sebastian -- everything evolves into decay

2 2

Twisted-based Tor client performance measurement tool
by Karsten Loesing 25 Jan '13

25 Jan '13

Hi everyone, you probably heard of Torperf [0], the tool that produces our Tor client performance graphs [1]. Torperf is mostly a bunch of scripts and lengthy HOWTOs, so setting it up and keeping it happy is not exactly trivial. The same applies to extending it, e.g., to make downloads using Selenium/Firefox rather than using its own C SOCKS client. I'm pondering a rewrite of Torperf in Twisted. The idea is to have a single Twisted application that is trivial to install and that does the following things: 1) set up local Tor clients, configure them, and register for events; 2) run a local web server to download files from or upload files to; 3) periodically run one or more tests which can be: 3.1) an HTTP GET request over Tor to its own web server, 3.2) an HTTP POST request to measure upload speed, 3.3) a GET or POST request to a locally running hidden service, 3.4) a series of fetches of top 50 Alexa domains using Selenium/Firefox; 3.5) a series of requests to track stream/circ allocations for #5830; 4) store request timestamps and Tor controller events to SQLite; 5) provide results via a RESTful API over its web server. That's a lot, and to make things even more fun, there's a sponsor deadline to have more realistic Torperf measurements by February 28. So, I want to start with 3.4 and minimal versions of 4 and 5. But I want to make sure that the remaining parts can be added later without redesigning everything again. My questions: - Is Twisted the right framework for this? What are the alternatives? - Is there existing code that I should look at before writing new code? - Does anybody want to help out? :) Thanks! Karsten [0] https://gitweb.torproject.org/torperf.git [1] https://metrics.torproject.org/performance.html

7 17

Re: [tor-dev] [tor-talk] Open streams on the fly
by benjaminlincoln＠lavabit.com 23 Jan '13

23 Jan '13

> On Mon, Jan 21, 2013 at 2:56 PM, <benjaminlincoln(a)lavabit.com> wrote: >>>> I see, tor already implements such a flag, ISO_STREAM. >> >> I attached a simple formal proposal for this idea. Please discuss. > > Proposals go to tor-dev, not tor-talk. > > Before you re-send, you should check out the discussion (what there is > of it) on ticket #7553 at > https://trac.torproject.org/projects/tor/ticket/7553 . The major > concern at the time was the performance impact from a large number of > users all activating this option. The discussion on the ticket has > stalled; it would be nice to reboot the discussion on tor-dev and try > to bring it to a conclusion. > > In particular, if people think *this* is a good way to "maintain > separate identities" for something like web browsing, that's an > accidental DOS attack waiting to happen. > > Following Nicks's advice I would like to start a discussion on ticket 7553. https://trac.torproject.org/projects/tor/ticket/7553 I think this feature should be exposed to the user. I refrained from writing "implemented" because this feature is already implemented. Not exposing it to the user will not stop Bad Guy(TM) from using it because it can easily be enabled by a trivial 2-line patch to tor. This will not lead to DOS. Circuits being created is slow for the user. I doubt anyone will enable this for real-time, interactive communication like surfing. It hurts anonymity, too. Cypherpunks patch mentions this. 895 **IsolateStream**;; 896 Don't share circuits at all, i.e. isolate each stream to an individual 897 circuit. (Not suitable for browsing or general use, where it *will hurt 898 your anonymity* due to the noisy request profile. The constant creation 899 of new circuits will also be excruciatingly slow for you and put 900 unnecessary load on the Tor network.) Most protocols, in particular HTTP(S), explicitly request their connections to be kept alive. IsolateStream will not have a real effect on these protocols.

2 1

Simple example in C
by monet＠tormail.org 21 Jan '13

21 Jan '13

Anybody can help me? I search a simple program in C to read information from hiden services in tor. Services is simple perl script. and only tcp

1 0

Re: [tor-dev] [tor-talk] Open streams on the fly
by benjaminlincoln＠lavabit.com 19 Jan '13

19 Jan '13

>> The implementation of proposal 171 and subsequent release of tor >> 0.2.3.25 >> fills my heart with joy. Yet, as far as I can tell, there is one use >> case >> that is not adequately covered. I would like to open and close Streams >> (TransPort's, DNSPort's and SOCKSPort's) at run-time without interfering >> with other, existing Streams and Circuits. SETCONF does not work here >> because it resets all existing streams. > > I think tor lacks an isolation flag which specifies to isolate each and > every stream, even those going to the same address and port. I see, tor already implements such a flag, ISO_STREAM. /** Isolate based on destination port */ #define ISO_DESTPORT (1u<<0) /** Isolate based on destination address */ ... /** Isolate all streams (Internal only). */ #define ISO_STREAM (1u<<7) diff --git a/src/or/config.c b/src/or/config.c index 90a5dfb..648bfba 100644 --- a/src/or/config.c +++ b/src/or/config.c @@ -5929,6 +5929,8 @@ parse_port_config(smartlist_t *out, isoflag = ISO_CLIENTPROTO; } else if (!strcasecmp(elt, "IsolateClientAddr")) { isoflag = ISO_CLIENTADDR; + } else if (!strcasecmp(elt, "IsolateStream")) { + isoflag = ISO_STREAM; } else { log_warn(LD_CONFIG, "Unrecognized %sPort option '%s'", portname, escaped(elt_orig)); This looks like a reasonable addition to me - an addition that could be backported to 0.2.3.x.

1 1

Affect of Proposal 207 on user metrics
by Abel Luck 18 Jan '13

18 Jan '13

Question: How does proposal 207 (relay fetching through entry guards) affect the user metric data? Is it possible to keep that data accurate (for the current value of accurate)? ~abel

2 1

Tor Browser repository for Fedora 17 and 18
by Jamie Nguyen 17 Jan '13

17 Jan '13

Hi, I'm the maintainer for Tor package on Fedora EPEL. I've set-up a (GPG signed) repository for Fedora 17 and 18 with Tor Browser RPM packages. It optionally includes SELinux protection for the Tor Browser. (Tor client/server already has SELinux protection on Fedora.) More info here: https://jamielinux.com/articles/2013/01/tor-and-tor-browser-repository-on-f… -- Jamie Nguyen

1 0

Multiple Tor
by Bin Wang 17 Jan '13

17 Jan '13

Dear Guys, I am brand new to TOR and I feel like multiple TORs should be considered. The multiple tors I mentioned here are not only multiple instances, but also using different proxy ports for each, like what has been done here http://www.howtoforge.com/ultimate-security-proxy-with-tor) I am trying to get started with 4 tors. However, the tutorial applies to Arch Linux and I am using a headless EC2 ubuntu 64bits. It is really a pain going through the differences between Arch and Ubuntu. And here I am wondering is there anyone could offer some help to implement my idea simplicitly. 1. Four TORs running at the same time each with an individual port, privoxy or polipo or whatever are ok once it works. Like: 8118 <- Privoxy <- TOR <- 9050 8129 <- Privoxy <- TOR <- 9150 8230 <- Privoxy <- TOR <- 9250 8321 <- Privoxy <- TOR <- 9350 2. In this way, if I try to return the ip of 127.0.0.1:8118, 8129, 8230 and 8321, they should return four different ips, which indicates there are four different tors running at the same time. Then, a few minutes later, check again, all four of them should have a new ips again. I know my simple 'dream' could come true in many ways, however... I am not only new to tor, but even also to bash and python... That is why I come here and see whether some of you could light me up. These links might be useful: http://blog.databigbang.com/distributed-scraping-with-multiple-tor-circuits/ https://www.torservers.net/wiki/setup/server#multiple_tor_processes http://www.howtoforge.com/ultimate-security-proxy-with-tor Best, Bin Wang

3 4

All the problems about Stegotorous
by vmonmoonshine＠gmail.com 16 Jan '13

16 Jan '13

Hello everybody, I was talking to Roger yesterday on the IRC, and he mentioned that "[S]tegotorus ... has a whole lot of problems". I have heard this many times in different forms by now (in Florence, The sponsor F discussion, etc). But I never saw these "lot of problems" are broken down in a list, so at least one can attack them one by one. It was always "lots of problem". So, let this email be an appeal to all of you who have some problem, deficiency, architectural dissatisfaction, etc with Stegotorus, write back on this thread, so at least we have written account of these problems and dissatisfactions? Then I'll turn them into the tickets as the very first step toward their solution. Also it can serve as written account of difficulties involving the making of any HTTP transport. Thank you for your contribution in advance. Cheers, Vmon

3 2