Re: [tor-dev] Pluggable Transports 2.0 Specification, Draft 2

> On 21 Jun 2017, at 14:27, David Fifield wrote: > > On Wed, Jun 21, 2017 at 01:16:20PM +1000, teor wrote: >> In general, is there a separate document or proposal that describes >> how Tor will implement the relevant interfaces? There doesn't seem >> to be much on

Re: [tor-dev] Pluggable Transports 2.0 Specification, Draft 2

On Wed, Jun 21, 2017 at 01:16:20PM +1000, teor wrote: > In general, is there a separate document or proposal that describes > how Tor will implement the relevant interfaces? There doesn't seem > to be much on Tor-specific issues in this spec. > > There is one "Tor" note in the spec, maybe it

[tor-dev] prop224: Time Period Overlaps and Blinded Keys

Hi, The time period overlap section 2.2.4 in prop224 is under-specified: https://gitweb.torproject.org/torspec.git/tree/proposals/224-rend-spec-ng.txt#n821 1. During the overlap period, does the service use the new blinded key for the new period, and the old blinded key for the old period? I

Re: [tor-dev] Pluggable Transports 2.0 Specification, Draft 2

Thanks for the feedback. I'll fix this in the next draft. On Jun 20, 2017 6:07 PM, "Yawning Angel" wrote: > On Tue, 20 Jun 2017 14:07:39 -0400 > Brandon Wiley wrote: > > > Attached is the second draft of the Pluggable Transport 2.0 > > Specification.

Re: [tor-dev] Pluggable Transports 2.0 Specification, Draft 2

On Tue, 20 Jun 2017 14:07:39 -0400 Brandon Wiley wrote: > Attached is the second draft of the Pluggable Transport 2.0 > Specification. If you have feedback on this draft, please send me > your comments by July 20. I'll raise this because it bothers me, but maybe the other

Re: [tor-dev] Pluggable Transports 2.0 Specification, Draft 2

Changelog from Draft 1 ● Renamed version flag to ptversion to avoid naming conflict with goptlib ● Modified Go examples to use correct Go syntax ● Renamed pt module in Go examples to base to avoid naming conflict with goptlib ● Reworded introduction ● Clarified Go examples with more details on