Re: [tor-dev] First five Tor tech reports

2012-07-17 Thread Roger Dingledine
On Thu, Jul 12, 2012 at 03:12:22PM +0200, Karsten Loesing wrote: > Hi Roger, hi Nick, > > here are the first five metrics tech reports that I'd like to turn into > Tor tech reports (see #5405 for the idea behind this). If you agree > that this is a good idea, I'll push the sources to tech-reports

Re: [tor-dev] Ports with hidden/rend services?

2012-07-17 Thread Kevin Evans
D'oh! I hope this wasn't the wrong place to ask this. I couldn't seem to find anywhere else to ask this. ___ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev

[tor-dev] Ports with hidden/rend services?

2012-07-17 Thread Kevin Evans
I am utterly dumbfounded by this (it's probably because I'm really tired), but in rendservice.c in the rend_service_t structure, there is a smartlist_t for the ports. How exactly are the [source and destination] ports stored in there? Thanks, Kevin ___ t

Re: [tor-dev] [OONI] Designing the OONI Backend (OONIB). RESTful API vs rsynch

2012-07-17 Thread Isis
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sun 15 Jul 2012 at 10:13, thus spake Tom Ritter: > > Contra: > > * No support for deltas (we can use rsych protocol over HTTP if we > > really need this). > > It's a little hackish, but I believe there is a 'standard' way to do > this in HTTP al

Re: [tor-dev] [OONI] Designing the OONI Backend (OONIB). RESTful API vs rsynch

2012-07-17 Thread Isis
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon 16 Jul 2012 at 02:15, thus spake Ondrej Mikle: > On 07/15/2012 02:56 PM, Arturo Filastò wrote: > > > > # What properties we would like it to have > > note: these are not ordered. > > * Efficient even over high latency networks. > > * Ease of

Re: [tor-dev] Clarification of prop 186

2012-07-17 Thread Linus Nordberg
Nick Mathewson wrote Tue, 17 Jul 2012 09:31:48 -0400: | Everything that describes how these documents are formatted describes | them as containing multiple "a" lines. Thus, anybody parsing a | consensus or microdescriptor MUST accept multiple "a" lines, even if | they ignore all but the first. |

Re: [tor-dev] Clarification of prop 186

2012-07-17 Thread Nick Mathewson
On Tue, Jul 17, 2012 at 12:24 AM, Linus Nordberg wrote: > Hi, > > Can votes and consensuses have more than one "a" line? Prop 186 says, on > one hand > > [...] votes should include a single "a" line for every relay that has > an IPv6 address, to include the first IPv6 line in its > descripto

Re: [tor-dev] Clarification of prop 186

2012-07-17 Thread Jeroen Massar
On 2012-07-17 06:24, Linus Nordberg wrote: > Hi, > > Can votes and consensuses have more than one "a" line? Prop 186 says, on > one hand > > [...] votes should include a single "a" line for every relay that has > an IPv6 address, to include the first IPv6 line in its > descriptor. [...] The