Re: [tor-dev] What are some aspects of Tor that are suffering right now due to lack of speed?

2014-07-24 Thread Roger Dingledine
On Fri, Jul 25, 2014 at 04:10:50AM +0100, Virgil Griffith wrote: > Hidden services quickly come to mind. > > Are there other candidates? I can imagine people deciding not to view > certain content through Tor because of speed (e.g., pornhub). But I > suspect I am missing some use cases. Hi Virg

[tor-dev] What are some aspects of Tor that are suffering right now due to lack of speed?

2014-07-24 Thread Virgil Griffith
Hidden services quickly come to mind. Are there other candidates? I can imagine people deciding not to view certain content through Tor because of speed (e.g., pornhub). But I suspect I am missing some use cases. -V ___ tor-dev mailing list tor-dev@li

Re: [tor-dev] Email Bridge Distributor Interactive Commands

2014-07-24 Thread isis
Nima Fatemi transcribed 4.0K bytes: > isis: > [...] > >> Are some of our least technical users, many of whom have never even seen a > >> command line before and who may live in Sub-Saharan Africa or one of the > >> Stan countries with only a rudimentary knowledge of English going to > >> understand

[tor-dev] New Version of OnionMail 1.6.0.667B is Out

2014-07-24 Thread Liste
* Thunderbird autoconfiguraticon. * Web Server. * User subscription webpages. * Full integrated PGP key generation and keyServer sender. * Mail Queue (onli exit/enter server). * Bash OnionMail Setup wizard. * And much more... You can activate an OnionMail server in 5 minutes! You can create a new

Re: [tor-dev] DEFAULT_ROUTE_LEN [was: Silly (or not so silly) question]

2014-07-24 Thread Yawning Angel
On Thu, 24 Jul 2014 16:48:21 -0400 grarpamp wrote: > On Wed, Jul 23, 2014 at 6:34 PM, Roger Dingledine > wrote: > > On Wed, Jul 23, 2014 at 11:24:47PM +0100, Noel David Torres Taño > > wrote: > >> What would happen if a Tor node changes behaviour and uses four or > >> five relay steps instead of

[tor-dev] DEFAULT_ROUTE_LEN [was: Silly (or not so silly) question]

2014-07-24 Thread grarpamp
On Wed, Jul 23, 2014 at 6:34 PM, Roger Dingledine wrote: > On Wed, Jul 23, 2014 at 11:24:47PM +0100, Noel David Torres Taño wrote: >> What would happen if a Tor node changes behaviour and uses four or five >> relay steps instead of three? At around DEFAULT_ROUTE_LEN 8 or above I get a lot of thes

Re: [tor-dev] Email Bridge Distributor Interactive Commands

2014-07-24 Thread Israel Leiva
Hi. I support what Philipp and Nima say about keywords. The given commands surely look simple for technical users, but what about non-technical users? If the purpose of the distributor is to give info, and you're already filtering emails to *try* to avoid fake requests (correct if i'm wrong), then

Re: [tor-dev] Email Bridge Distributor Interactive Commands

2014-07-24 Thread harmony
Nima Fatemi : > > I think "bridges" works just fine for "vanilla bridges" and I want to > take the opportunity to +1 Philipp's idea on looking for keywords > instead of commands, regardless of how they're phrased. Help desk frequently sees bridge keywords in other (supported/unsupported) language

Re: [tor-dev] channel_t to IP Address

2014-07-24 Thread Andrea Shepard
On Thu, Jul 24, 2014 at 01:55:43PM +0100, Gareth Owen wrote: > Andrea > > Thanks for taking the time to reply and for the advice. I have just this > second discovered this method: > > TO_OR_CIRCUIT(circ)->p_chan->get_remote_descr(TO_OR_CIRCUIT(circ)->p_chan, > 0) > > which returns the endpoint

Re: [tor-dev] channel_t to IP Address

2014-07-24 Thread Gareth Owen
Andrea Thanks for taking the time to reply and for the advice. I have just this second discovered this method: TO_OR_CIRCUIT(circ)->p_chan->get_remote_descr(TO_OR_CIRCUIT(circ)->p_chan, 0) which returns the endpoint as a string. I wonder, is this safer/future proof or should this approach be d

Re: [tor-dev] channel_t to IP Address

2014-07-24 Thread Andrea Shepard
On Thu, Jul 24, 2014 at 12:20:52PM +0100, Gareth Owen wrote: > Hi all > > Quick question, how does one turn channel_t into an IP address, e.g. given > a circuit_t how do I get the IP address of the previous and next hop > (noting that they might not be in the consensus so I cant use the identity >

[tor-dev] channel_t to IP Address

2014-07-24 Thread Gareth Owen
Hi all Quick question, how does one turn channel_t into an IP address, e.g. given a circuit_t how do I get the IP address of the previous and next hop (noting that they might not be in the consensus so I cant use the identity hash). I can see the information is in the connection_t struct but I do

Re: [tor-dev] Email Bridge Distributor Interactive Commands

2014-07-24 Thread Griffin Boyce
isis wrote: Do you have a better suggestion for what to call "vanilla bridges"? I keep calling them standard bridges (as opposed to fancy, monocle-wearing bridges). People seem to understand immediately that other types of bridges are special somehow if I call regular/vanilla/non-obfs bri

Re: [tor-dev] Email Bridge Distributor Interactive Commands

2014-07-24 Thread Noel David Torres Taño
El jue, 24-07-2014 a las 06:54 +, Nima Fatemi escribió: > isis: > [...] > >> Are some of our least technical users, many of whom have never even seen a > >> command line before and who may live in Sub-Saharan Africa or one of the > >> Stan countries with only a rudimentary knowledge of English

Re: [tor-dev] Email Bridge Distributor Interactive Commands

2014-07-24 Thread Nima Fatemi
isis: [...] >> Are some of our least technical users, many of whom have never even seen a >> command line before and who may live in Sub-Saharan Africa or one of the >> Stan countries with only a rudimentary knowledge of English going to >> understand the difference between vanilla bridges and, say

Re: [tor-dev] Email Bridge Distributor Interactive Commands

2014-07-24 Thread isis
Ken Keys transcribed 3.4K bytes: > On 7/23/2014 10:57 AM, Matt Pagan wrote: > > > >>> COMMANDs: (combine COMMANDs to specify multiple options simultaneously) > >>> get bridgesRequest vanilla bridges. > >>> get transport [TYPE] Request a Pluggable Transport by TYPE. > >>> get hel