Debian Bug report logs - #764007
RFP: meek -- Pluggable transport to circumvent IP address blocking via public services

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Ximin Luo <infinity0@pwned.gg>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: ITP: meek -- Pluggable transport to circumvent IP address blocking via public services

Date: Thu, 02 Oct 2014 18:48:21 +0100

Package: wnpp
Severity: wishlist
Owner: Ximin Luo <infinity0@pwned.gg>

* Package name    : meek
  Version         : 0.12
  Upstream Author : David Fifield <david@bamsoftware.com>
* URL             : https://trac.torproject.org/projects/tor/wiki/doc/meek
* License         : CC0 1.0 Universal
  Programming Lang: Go
  Description     : Pluggable transport to circumvent IP address blocking via public services

Meek is a tool to circumvent censorship by relaying traffic through a
third-party server that is hard to block, for example a ​CDN. It uses a trick
called "domain fronting" to talk to a Tor relay-like service while appearing
to talk to another domain. The traffic itself is HTTPS, aiming to look like a
typical encrypted web session.

This is similar in many respects to flashproxy-client/pt-websocket.
I will be maintaining this as part of the Debian Go Packaging Team.

Message #10 received at 764007@bugs.debian.org (full text, mbox, reply):

From: Patrick Schleizer <adrelanos@riseup.net>

To: 764007@bugs.debian.org

Date: Fri, 31 Jul 2015 10:23:44 +0000

What's the status of this?

Cheers,
Patrick

Message #15 received at 764007@bugs.debian.org (full text, mbox, reply):

From: Ximin Luo <infinity0@pwned.gg>

To: Patrick Schleizer <adrelanos@riseup.net>, 764007@bugs.debian.org

Subject: Re: Bug#764007: (no subject)

Date: Fri, 31 Jul 2015 12:33:39 +0200

[Message part 1 (text/plain, inline)]

On 31/07/15 12:23, Patrick Schleizer wrote:
> What's the status of this?
> 

Waiting on https://trac.torproject.org/projects/tor/ticket/12716

Help with it would be appreciated. :) As soon as that is merged, I will upload meek.

If you can't help, you can also find preliminary packages here: https://mentors.debian.net/package/meek

X

-- 
GPG: 4096R/1318EFAC5FBBDBCE
git://github.com/infinity0/pubkeys.git

[signature.asc (application/pgp-signature, attachment)]

Message #28 received at 764007@bugs.debian.org (full text, mbox, reply):

From: Ximin Luo <infinity0@pwned.gg>

To: 764007@bugs.debian.org

Cc: Patrick Schleizer <adrelanos@riseup.net>, bartm@debian.org

Subject: Re: Bug#764007: (no subject)

Date: Sat, 05 Nov 2016 14:18:00 +0000

Ximin Luo:
> On 31/07/15 12:23, Patrick Schleizer wrote:
>> What's the status of this?
> 
> Waiting on https://trac.torproject.org/projects/tor/ticket/12716
> 
> Help with it would be appreciated. :) As soon as that is merged, I will upload meek.
> 
> If you can't help, you can also find preliminary packages here: https://mentors.debian.net/package/meek
> 

To confirm, I still Intend To Package this piece of software. I am waiting on a reply to ticket 12716. My Intent To Package this software will *never expire*, so please do not change it to an RFP "for inactivity" or any other reason.

After 12716 is resolved, this piece of software can be in Debian *within the next day*, or 2-3 hours if luck has it.

Anyone that is interested in seeing meek in Debian should contact the upstream author, David Fifield, to ask him to respond to that ticket. More people would help - I don't wish to ping the same ticket 5 times, I have other things to do with my time.

Frankly, I don't know why he hasn't responded. I won't single out his address here, but it is easy enough to find. Yes, he is still maintaining meek and making updates to it - see the upstream git.

If he does not take ticket #12716 seriously, that is a signal to me that meek should not enter Debian. The browser plugin is vital to offer a good level of protection against fingerprinting. If it is necessary for Tor Browser users, it is necessary for Debian.

I will not have a piece of software that treats Debian users as second-class citizens - we deserve more respect than that, especially given what Debian has contributed to Free and Open Source Software over all these years - and I will block other people from packaging this software in such a degrading way, if so necessary.

However as I said, I will always Intend To Package meek.

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Message #33 received at 764007@bugs.debian.org (full text, mbox, reply):

From: iry <iry@riseup.net>

To: 764007@bugs.debian.org

Date: Wed, 13 Sep 2017 06:10:27 +0000

[Message part 1 (text/plain, inline)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi Ximin Luo!

It seems that the upstream author has respond:
https://trac.torproject.org/projects/tor/ticket/12716#comment:33

For the convenience of the future discussion, I am citing the respond
inline:

> meek-client-torbrowser has only gotten more tightly coupled to Tor 
> Browser, with #18371, #18904, #19646. meek-client-torbrowser is 
> unlikely now ever to work for ordinary Firefox.
> 
> My advice is make a separate meek-client-wrapper or 
> meek-client-debian or something, perhaps by forking an older 
> version of meek-client-torbrowser. The code for it could be 
> maintained in the Debian package (it's not much code) along with 
> whatever xvfb or other auxiliary code Debian needs. I'm also 
> willing to have a generic or Debian-specific in the main meek 
> source tree, if that's better for the Debian maintainers.
> 
> Another alternative is just to ignore the browser camouflage layer 
> on Debian. That's what every other nonTor Browser platform already 
> does, as far as I know.

Could you please tell me the status of this package?

Thank you very much!

Best,
iry
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJZuMvWAAoJEKFLTbxtzdU8BwAP/A/617waaSWnfpSArQ1kJrId
jwgDRTPse2/5fi8kKPNeNkgGZkv2QF7FU6X7rGMZj5Bwaspes61YCDbPTZ24Da6I
CwrUAcldTJtuXW+bcU6j+mTJH1v+7N02vBSzeLJNVAog8i+kxG6K8zHERD5HoFT8
hEQVQfqYRdH0/hJ6PwAh+2UaMdWGXWBxnyjeV9crmQJLEh4krO2NDGtbXhmOoOTj
75ODeP/34cJ/evYy4w8mskydp5uHYbQjTdO6vw4aanEtM5cNbGmmDLSfI2yOnWDH
oLWxC865YftG6JzwCwzOLLWtDOlz4/X4wmSRExN1TN23/3o+QxuLtv7F9xZiEuM3
gLj/yI+IBPBu4XYgdqAo8MaV1dbMxUMecQv7CYpLUucCNzpS2wStwCAelCIQhlYb
2WyIKl5HIewfvVZ4Mp8c1NfjGgwE4rJxm6v8SLpJc1bADcj484WPI1OVgKvGQwgx
ckKGvqI/DZRMuPgqgYQq060QlGBlvMa2v5XoFO3bMgHxlS/+mQxo486ybZYRWqYs
X0CCb/wHV0Q15p14lrRGDEOc6r7HNDe2Q5jEM/IcJ5pCzkkkLfHDvolFW1r1DkWn
UOr8WpbkPNRJnSDaOqpKXSs+68XSKNqlrfkq7XAnsBHQHyx76m77XNIM9ghI/MOA
FnIfTZ44IbreXHr02v4s
=+sv9
-----END PGP SIGNATURE-----

[0x6DCDD53C.asc (application/pgp-keys, attachment)]

[0x6DCDD53C.asc.sig (application/pgp-signature, attachment)]

Message #38 received at 764007@bugs.debian.org (full text, mbox, reply):

From: Ximin Luo <infinity0@debian.org>

To: iry <iry@riseup.net>, 764007@bugs.debian.org

Subject: Re: Bug#764007: (no subject)

Date: Wed, 13 Sep 2017 08:29:00 +0000

iry:
> Hi Ximin Luo!
> 
> It seems that the upstream author has respond:
> https://trac.torproject.org/projects/tor/ticket/12716#comment:33
> 
> For the convenience of the future discussion, I am citing the respond
> inline:
> 
>> meek-client-torbrowser has only gotten more tightly coupled to Tor 
>> Browser, with #18371, #18904, #19646. meek-client-torbrowser is 
>> unlikely now ever to work for ordinary Firefox.
> 
>> My advice is make a separate meek-client-wrapper or 
>> meek-client-debian or something, perhaps by forking an older 
>> version of meek-client-torbrowser. The code for it could be 
>> maintained in the Debian package (it's not much code) along with 
>> whatever xvfb or other auxiliary code Debian needs. I'm also 
>> willing to have a generic or Debian-specific in the main meek 
>> source tree, if that's better for the Debian maintainers.
> 
>> Another alternative is just to ignore the browser camouflage layer 
>> on Debian. That's what every other nonTor Browser platform already 
>> does, as far as I know.
> 
> Could you please tell me the status of this package?
> 

I responded on the ticket. If you like, you can try writing a new patch as I described in my response, and ask upstream to merge that one.

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Send a report that this bug log contains spam.