Re: [tor-dev] Proposal 190: Password-based Bridge Client Authorization

2012-01-17 Thread Robert Ransom
On 2012-01-17, Ian Goldberg wrote: > On Tue, Jan 17, 2012 at 08:43:00PM +0200, George Kadianakis wrote: >> [0]: Did the Telex people clean up the patch, generalize it, and post >> it in openssl-dev? Having configurable {Server,Client}Hello.Random in >> a future version of OpenSSL would be neat. >

Re: [tor-dev] Proposal 190: Password-based Bridge Client Authorization

2012-01-17 Thread Ian Goldberg
On Tue, Jan 17, 2012 at 08:43:00PM +0200, George Kadianakis wrote: > [0]: Did the Telex people clean up the patch, generalize it, and post > it in openssl-dev? Having configurable {Server,Client}Hello.Random in > a future version of OpenSSL would be neat. At USENIX Security, Adam opined that opens

Re: [tor-dev] Proposal 190: Password-based Bridge Client Authorization

2012-01-17 Thread George Kadianakis
Nick Mathewson writes: > On Sun, Nov 6, 2011 at 9:12 PM, George Kadianakis wrote: > >> 3.2. AUTHORIZE cell format >> >>   In shared-secret-based authorization, the MethodFields field of the >>   AUTHORIZE cell becomes: >> >>       'shared_secret'               [10 octets] >> >>   where: >> >>  

Re: [tor-dev] Proposal 190: Password-based Bridge Client Authorization

2012-01-17 Thread Robert Ransom
On 2012-01-17, Nick Mathewson wrote: > On Sun, Nov 6, 2011 at 9:12 PM, George Kadianakis > wrote: > >> 3.2. AUTHORIZE cell format >> >> In shared-secret-based authorization, the MethodFields field of the >> AUTHORIZE cell becomes: >> >> 'shared_secret' [10 octets] >> >>

Re: [tor-dev] Proposal 190: Password-based Bridge Client Authorization

2012-01-17 Thread Nick Mathewson
On Sun, Nov 6, 2011 at 9:12 PM, George Kadianakis wrote: > 3.2. AUTHORIZE cell format > >   In shared-secret-based authorization, the MethodFields field of the >   AUTHORIZE cell becomes: > >       'shared_secret'               [10 octets] > >   where: > >   'shared_secret', is the shared secret

Re: [tor-dev] Proposal 186: Multiple addresses for one OR or bridge

2012-01-17 Thread Fabio Pietrosanti (naif)
On 1/17/12 5:41 PM, Nick Mathewson wrote: >>> >>> ORPort 1337 no-advertise alladdrs >>> ORPort tornode.example.com:443 no-bind alladdrs >> >> This drives home the issue with alladdrs: what would we do if that flag >> isn't listed here? This feature would allow a single node, for example,

Re: [tor-dev] Proposal 186: Multiple addresses for one OR or bridge

2012-01-17 Thread Nick Mathewson
On Sun, Oct 23, 2011 at 1:26 PM, Roger Dingledine wrote: > [Quoting the original mail, but it's actually the file in git that I > read and am commenting on.] > > On Wed, Sep 21, 2011 at 02:13:18PM -0400, Nick Mathewson wrote: >>   The 'AllAddrs' option tells Tor that if no address is given in the

Re: [tor-dev] Filtering of DA and bootstrap

2012-01-17 Thread Nick Mathewson
On Tue, Jan 17, 2012 at 3:15 AM, Fabio Pietrosanti (naif) wrote: > Hi all, > > in a network where the Directory Authority hard-coded in Tor code are > filtered a Tor client cannot bootstrap. > > But as far as i understood there are (hundreds?) of Tor DA Mirror. > > If so, packaging the Tor clients

[tor-dev] Filtering of DA and bootstrap

2012-01-17 Thread Fabio Pietrosanti (naif)
Hi all, in a network where the Directory Authority hard-coded in Tor code are filtered a Tor client cannot bootstrap. But as far as i understood there are (hundreds?) of Tor DA Mirror. If so, packaging the Tor clients periodically, bundling the latest consensus with the software, would provide h