[tor-dev] [Applications Team] First meeting next Tuesday 19:00 UTC

2015-10-29 Thread Georg Koppen
Hi, just a reminder that the applications team is starting the monthly meetings next week on Tuesday, November 3 at 19:00 UTC[0] in #tor-project on irc.oftc.net. The proposed topic is still talking about UX/internationalization issues. If there are other things worth discussing we can easily amen

Re: [tor-dev] [proposal] New Entry Guard Selection Algorithm

2015-10-29 Thread Nick Mathewson
On Thu, Oct 29, 2015 at 5:01 PM, isis wrote: > Hello, > > For your reviewing pleasure, may I present you with a new (draft) proposal for > a new entry guard selection algorithm, and associated data structures (with > reference implementations!). [0] The bulk of it is based upon George > Kadianaki

[tor-dev] Tor Messenger Beta: Chat over Tor, Easily

2015-10-29 Thread Sukhbir Singh
Hi, Today we are releasing a new, beta version of Tor Messenger, based on Instantbird [0], an instant messaging client developed in the Mozilla community. * What is it? Tor Messenger is a cross-platform chat program that aims to be secure by default and sends all of its traffic over Tor. It sup

[tor-dev] [proposal] New Entry Guard Selection Algorithm

2015-10-29 Thread isis
Hello, For your reviewing pleasure, may I present you with a new (draft) proposal for a new entry guard selection algorithm, and associated data structures (with reference implementations!). [0] The bulk of it is based upon George Kadianakis' recent email and pseudocode. [1] [2] There are still

[tor-dev] Proposal 258: Denial-of-service resistance for directory authorities

2015-10-29 Thread Nick Mathewson
[Here's a new proposal from Andrea. See ticket 4581 for implementation details.] Filename: 258-dirauth-dos.txt Title: Denial-of-service resistance for directory authorities Author: Andrea Shepard Created: 2015-10-27 Status: Open 1. Problem statement The directory authorities are few in numb

Re: [tor-dev] Pluggable Transports v1 spec rewrite.

2015-10-29 Thread Yawning Angel
On Thu, 29 Oct 2015 10:27:53 -0400 Nathan Freitas wrote: > Any small or big changes to highlight that push us to the more > accessible goal? Well, it emphasizes that it's generic, gives a better view of the architecture, and should be usable by anyone competent (unless my rewrite is bad) to add

Re: [tor-dev] Pluggable Transports v1 spec rewrite.

2015-10-29 Thread Brandon Wiley
Excellent work on the rewrite. To summarize for those that do not have time to read the whole document, it's the same spec, it's just been rewritten to read more clearly. I think it's a great improvement over the previous version. I have two suggestions: Section 4, "Tor Configuration", I think sh

Re: [tor-dev] Pluggable Transports v1 spec rewrite.

2015-10-29 Thread Nathan Freitas
On Thu, Oct 29, 2015, at 09:19 AM, Yawning Angel wrote: > Hello all, > > In an attempt to make Pluggable Transports more accessible to other > people, and to have a spec that is more applicable and useful to other > projects that seek to use Pluggable Transports for circumvention, I have > drafted

Re: [tor-dev] Pluggable Transports v1 spec rewrite.

2015-10-29 Thread Hugo Maxwell Connery
Hi, A commendable effort. It is both deserved and pleasant that Tor hold the "gold standard" for a low latency, privacy enhancing, distributed, collaborative network. A perhaps more crowning achievement could be the fostering of a diverse ecosystem of related technologies. This effort continue

Re: [tor-dev] Update of prop#250: Random Number Generation During Tor Voting

2015-10-29 Thread George Kadianakis
teor writes: >> On 29 Oct 2015, at 05:26, David Goulet wrote: >> >> Finally, we would like your opinion also on if we should keep the >> conflict mechanism or not?. Since those partition attacks are basically >> dumb, do not achive much result for an attacker and it's at a high cost >> of compr

[tor-dev] Pluggable Transports v1 spec rewrite.

2015-10-29 Thread Yawning Angel
Hello all, In an attempt to make Pluggable Transports more accessible to other people, and to have a spec that is more applicable and useful to other projects that seek to use Pluggable Transports for circumvention, I have drafted a re-write of the spec. This is not intended to alter existing beh