Re: [tor-dev] grabbing Tor circuit (node) data- Tor stem, torrc and Tor control port

2013-06-10 Thread Damian Johnson
Hi Sarah. I'm not really sure what you're trying to ask in most of these questions. Assuming that your goal is simply 'I want to connect to port 9051 and dump information about all the relays I'm presently using in my circuits' then the following should do the trick. Take the following with a grai

Re: [tor-dev] Metrics Plans

2013-06-10 Thread Kostas Jakeliunas
Ah, forgot to add my footnote to the dirspec - we all know the link, but in any case: [1]: https://gitweb.torproject.org/torspec.git/blob/HEAD:/dir-spec.txt This was in the context of discussing which fields from 2.1 to include. On Tue, Jun 11, 2013 at 12:34 AM, Kostas Jakeliunas wrote: > > Her

Re: [tor-dev] Remote descriptor fetching

2013-06-10 Thread Kostas Jakeliunas
Hi folks! > Indeed, this would be pretty bad. I'm not convinced that moria1 > provides truncated responses though. It could also be that it > compresses results for every new request and that compressed responses > randomly differ in size, but are still valid compressions of the same > input. K

Re: [tor-dev] Metrics Plans

2013-06-10 Thread Kostas Jakeliunas
> > > Here, I think it is realistic to try and use and import all the fields > available from metrics-db-*. > > My PoC is overly simplistic in this regard: only relay descriptors, and > only a limited subset of data fields is used in the schema, for the import. > > I'm not entirely sure what fields

Re: [tor-dev] Metrics Plans

2013-06-10 Thread Kostas Jakeliunas
Hi! >>> Maybe we should focus on a 'grand unified backend' rather than > >>> splitting Kostas' summer between both a backend and frontend? If he > >>> could replace the backends of the majority of our metrics services > >>> then that would greatly simplify the metrics ecosystem. > >> > >> I'm most

Re: [tor-dev] traversing the source code of tor

2013-06-10 Thread Nick Mathewson
On Thu, Jun 6, 2013 at 5:17 PM, H S wrote: > Hi there, > We would like to implement some specific protocol in Tor as an > implementation project. > Our one of pseudo codes that we have to take into account is the one > mentioned on the paper under the link > http://www.cypherpunks.ca/~iang/pubs/UC

[tor-dev] grabbing Tor circuit (node) data- Tor stem, torrc and Tor control port

2013-06-10 Thread SARAH CORTES
Damian, thanks, this is very helpful. is there a way to do this in torrc? Else, i suppose i will need to: 1) create a socket or connection to my port 9051 ; do i need/can i use TORRC_CONTROL_SOCKET ? 2) call get_circuits() ; grab the relay fingerprints

Re: [tor-dev] stem

2013-06-10 Thread Damian Johnson
> Hi, Damian, thanks. I am happy to discuss it on tor-dev@. But I want to keep > off spam, which some of my questions at first may be, essentially Qs. But, > if you think they would be of interest to tor-dev, or others could help, > just let me know, and i will sign up for it. They certainly are!

Re: [tor-dev] Discussion on the crypto migration plan of the identity keys of Hidden Services

2013-06-10 Thread George Kadianakis
Mike Perry writes: > adrelanos: >> George Kadianakis: >> > If we move to the higher security of (e.g.) 128-bits, the base32 string >> > suddenly becomes 26 characters. Is that still conveniently sized to pass >> > around, or should we admit that we failed this goal and we are free to >> > crank u

Re: [tor-dev] Client simulation

2013-06-10 Thread Karsten Loesing
On 6/7/13 8:04 PM, Norman Danner wrote: > On 6/7/13 2:37 AM, Karsten Loesing wrote: >> (Sorry for cross-posting, but I think this is a topic for tor-dev@, not >> tor-talk@. If you agree, please reply on tor-dev@ only. tor-talk@ >> people can follow the thread here: > > OK, following up on tor-de