Re: [tor-dev] Slight obfsproxy API change (#10342)

2013-12-12 Thread Ximin Luo
On 12/12/13 23:40, George Kadianakis wrote: > David Stainton writes: > >> Excellent! I was thinking of making this change but lately I haven't had >> much time. >> Merging that patch specified in the 1st ticket comment? That looks good. >> >> I'd be happy to update the bananaphone transport to us

Re: [tor-dev] Slight obfsproxy API change (#10342)

2013-12-12 Thread George Kadianakis
David Stainton writes: > Excellent! I was thinking of making this change but lately I haven't had > much time. > Merging that patch specified in the 1st ticket comment? That looks good. > > I'd be happy to update the bananaphone transport to use the new api! > > Cheers, > > David > The change is

Re: [tor-dev] Slight obfsproxy API change (#10342)

2013-12-12 Thread David Stainton
Excellent! I was thinking of making this change but lately I haven't had much time. Merging that patch specified in the 1st ticket comment? That looks good. I'd be happy to update the bananaphone transport to use the new api! Cheers, David On Wed, Dec 11, 2013 at 10:33 PM, George Kadianakis w

Re: [tor-dev] Slight obfsproxy API change (#10342)

2013-12-11 Thread Philipp Winter
On Wed, Dec 11, 2013 at 09:33:47PM +, George Kadianakis wrote: > Do you agree with the changes? If yes, I will merge Ximin's patch for > #10342, and you will have to update your transport codebase > appropriately. Please let me know. For the record, I'm OK with this and replied here: https://t

[tor-dev] Slight obfsproxy API change (#10342)

2013-12-11 Thread George Kadianakis
Hello Philipp and David, I'm sending you an email because you are the people who are currently developing obfsproxy modules. We are thinking of slightly changing the API of obfsproxy, so that it becomes more friendly to transport authors (or at least we hope so). Specifically, we are thinking of