On Tue, 7 Jan 2020 10:36:20 +0100 Ulrike Uhlig <ulr...@debian.org> wrote: > On 07.01.20 10:14, Ulrike Uhlig wrote: > > On 07.01.20 00:57, Chris Lamb wrote: > > >> There is a new upstream release of obfs4proxy available (at the time > >> of writing, 0.0.11):>> However, this will require the packaging of at least https:// > >> gitlab.com/yawning/utls. > > > > Quoting Ana Custura: > > > > " > > We have 2 options going forward: we can package yawning's fork of uTLS > > or we can drop meek-lite support from the obfs4proxy package. We need to > > carefully consider this, as it is the only meek client currently > > packaged in Debian. I have built a package that drops meek-lite support > > (which is easily disabled) of version 0.0.11. > > > > There are some licensing issues that need to be resolved with yawning's > > fork of uTLS [3] before we consider looking at packaging it. > > Thinking about this a bit more I think it might also be worth asking Tor > (for example via irl@d.o or Philipp Winter, the lead of the censorship > team at Tor, https://nymity.ch/contact.txt) if they have a preferred way > of moving forward. > > Tor seems to have had plans to help with the maintenance apparently: > https://trac.torproject.org/projects/tor/ticket/29286 > > -- ulrike > >
Hey, I'm new to the debian packaging space but am happy to help out here. FWIW, there is active interest in a meek client package for Debian [1]. Before going forward with dropping it from the obfs4proxy package, we should probably have a meek package to take it's place. I've no idea how many tools rely on this feature of obfs4proxy but don't want to assume none. If I understand correctly, the main blocker on this is licensing concerns around Yawning's fork of utls? Perhaps it's better to resolve this as the path forward. I'll take a look and see what we can do about this. [1] https://trac.torproject.org/projects/tor/ticket/13160 - cecylia
