Re: [tor-dev] Enhancement for Tor 0.3.4.x

[George Kadianakis]

Nick Mathewson  writes:

> [ text/plain ]
> On Mon, Feb 12, 2018 at 2:32 PM, David Goulet  wrote:
>> Hello everone!
>>
>> As an effort to better organize our 0.3.4.x release for which the merge 
>> window
>> opens in 3 days (Feb 15th, 2018), we need to identify the enhancement(s) that
>> we want so we can better prioritize the development during the merge window
>> timeframe (3 months).
>>
>> Each feature should have its ticket marked for 0.3.4 milestone and with an
>> Owner set so we know who is "leading" that effort. It doesn't have to be the
>> person who code the whole thing but should be a good point of contact to 
>> start
>> with (and it can change over time as well).
>>
>> It is possible that an enhancement can have more than one ticket so in this
>> case, please make a "parent" ticket that explains the whole thing and child
>> tickets assigned to it.
>>
>> The network team just had its weekly meeting and if I recall correctly, these
>> enhancement should be planned for 0.3.4 (please the people who works on this,
>> can you tell us the tickets and make sure they are up to date?)
>>
>> - Privcount (prop#280)
>> - large CREATE cells (prop#249)
>>
>> If you plan to do a set of patches for a feature or enhancement, please do
>> submit it on this thread and make sure a proper ticket exists with an Owner.
>
> My biggest additional wishlist items for 0.3.4 are:
>
>   * ZSTD tuning (#24368)
>   * Fewer wakeups when idle (#14039)
>
> And as a reach:
>   * Improved TLS 1.3 support
>

Hello,

I agree it's a great idea to prioritize features for the next releases
so that we don't go blind!

Question wrt TLS 1.3: Is it lots of work to support TLS 1.3? And what
do we gain by supporting it? Should we prioritize it for this release or
for a subsequent one?

Cheers!
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev

Re: [tor-dev] Enhancement for Tor 0.3.4.x

[teor]

> On 20 Feb 2018, at 04:14, David Goulet  wrote:
> 
> The other part would be IPv6 for HSv3. This includes:
> 
> - Unify link specifier API/ABI (#22781)
> - Put IPv6 link specifiers in client EXTEND cells (#24451)
> - Put IPv6 and unrecognised link specifiers in onion service EXTEND cells
>  (#24181)
> - Put IPv6 link specifier in HS descriptor. (not ticket afaict).
> 
> There is a huge amount of IPv6 tickets with different tasks, I'll create a top
> level parent "Hidden service v3 IPv6 support" ticket and child many tickets
> related to this because right now it is hella confusing so we can consolidate
> in one place and track progress there. It should also include single onion.
> 
> It will for sure touches other part of Tor that aren't HS specific so
> hopefully we can overlap this with useful IPv6 implementation work.

I don't know how much time I will have to work on IPv6 in 0.3.4.
But I can prioritise reviewing proposals and code, and revising my existing
code.

Here are some dependencies:

HSv3 IPv6 needs relays to allow IPv6 extends:
#24404 Propose a relay protover that allows IPv6 extends

We also wanted to make relays do IPv6 extends first, to create cover traffic:
#24403 Propose and implement IPv6 ORPort reachability checks on relays

But we can use a consensus parameter instead:
#24868 Check a consensus parameter before activating onion service IPv6 features

T
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev

Re: [tor-dev] Enhancement for Tor 0.3.4.x

[David Goulet]

On 12 Feb (14:32:41), David Goulet wrote:
> Hello everone!
> 
> As an effort to better organize our 0.3.4.x release for which the merge window
> opens in 3 days (Feb 15th, 2018), we need to identify the enhancement(s) that
> we want so we can better prioritize the development during the merge window
> timeframe (3 months).

On my part, I plan to have some scheduler refactoring/changes that requires
quite a bit of changes in the scheduler architecture but overall should
simplify greatly things with Vanilla and KIST (and future schedulers).

- Parent ticket: #23993
  All child tickets are fixes that need to happen for this.
- This will touch also our circuit multiplexing and the connection subystem as
  well (mostly how the outbuf interacts with the scheduler).

The other part would be IPv6 for HSv3. This includes:

- Unify link specifier API/ABI (#22781)
- Put IPv6 link specifiers in client EXTEND cells (#24451)
- Put IPv6 and unrecognised link specifiers in onion service EXTEND cells
  (#24181)
- Put IPv6 link specifier in HS descriptor. (not ticket afaict).

There is a huge amount of IPv6 tickets with different tasks, I'll create a top
level parent "Hidden service v3 IPv6 support" ticket and child many tickets
related to this because right now it is hella confusing so we can consolidate
in one place and track progress there. It should also include single onion.

It will for sure touches other part of Tor that aren't HS specific so
hopefully we can overlap this with useful IPv6 implementation work.

That is it for now, in terms of features, I think this is reasonable to be
completed and merged in the next 3 months for 034 merge window.

Cheers!
David

-- 
s2OgTxgPSliwm2a67jagCGlxYAy4npmC5/sM0nssJR0=


signature.asc
Description: PGP signature
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev

[tor-dev] Cross compiling Tor for Windows

[Alexander Færøy]

Hello.

I have recently been trying to wrap my head around some of the
Windows/Unix I/O code of Tor to do an API experiment with the PT
subsystem.

While working on this I remembered that Nick did a cool trick during the
development of the consensus diff feature where he managed to reproduce
a Windows only test case failure with Wine on Linux using a cross
compiled version of Tor that he build on Linux as well.

I wanted to try out if I was able to make use of this "trick" as well
and decided to write a short guide for setting up the cross compilation
environment for Tor on Debian. The guide is published at
https://github.com/ahf/tor-win32

The tor-win32 repository also contains a Makefile that will fetch and
cross compile a minimal set of dependencies of Tor (OpenSSL, Libevent,
and zlib) and Tor itself to the point where you should be able to run
both tor.exe and the test suites in Wine.

I hope this might be useful to someone else if they find themselves
having a need to quickly try something out on "Windows" without actually
having to install it -- remember though that this is not the same as
running Tor and the test suites on an actual Windows machine, which is
what many of our users are using! :-)

Cheers,
Alex.

-- 
Alexander Færøy
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev