Vidalia Relay Bundle(win) Tor version, obfs4proxy package in deb.tp.o
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 1. I have noticed that the Vidalia Relay Bundles for Windows available to download on torproject.org are using Tor 0.2.4.23, while we are on 0.2.5.10 as stable branch. I know 0.2.4.23 is still on the recommended list in the consensus, but since someone is downloading the bundles fresh from the Tor home page, I think it is expected to include the latest stable Tor version. 2. Configured some obfs4 bridges using obfs4proxy. They work very good, however it's a little bit complicated since package obfs4proxy exists in Debian sid, but not in deb.torproject.org, so you have to add sid repo to sources.list, install obfs4proxy and then make sure you edit apt preferences or comment the sid repo from the list in order not to upgrade you entire Debian system with packages from unstable/testing branch. Received couple of emails from users wanted to deploy obfs4 bridges and were confused. Is it possible to include obfs4proxy in deb.torproject.org for Debian, and while at it also make a rpm package for RHEL/CentOS? obfsproxy (python based pluggable transport) was easy to install in RHEL/CentOS using EPEL repo and `pip` but obfs4proxy should come as a rpm from deb.torproject.org. 3. Last thing, the page https://bridges.torproject.org/ does not contain obfs4 in the drop-down list where the user needs to select the pluggable transport. It only allows requests for obfs2, obfs3, scramblesuit and fteproxy bridges. Don't know about fteproxy, but shouldn't obfs2 be deprecated or is it still working/used? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJUTRBeAAoJEIN/pSyBJlsR2zwH/2mnA2GNomxNQZI7Eeumt1sM uA6iXvlUiILJdQRG8EcHx8sfHU5MD20V5mOH774XsX7elAG47/ePL+/SKL69OfuR nl/X4IzH34CaqbMLGVHotl9Bcugfgw71fAF+Gm5nymM8VRxsdQnS51nnz7pwphon /DeeMfCE45eCYpVYyOqXZcSM4DA6Hr5bWG5TlCVJXTOl67fMr/pEBFgfpc6RIAL/ 8GXk+Cv6k/vW0AsEb/XoHBNbIzfHhOlb9O9q3giq3kGmJahMheKKLVOP5FNiEWi1 S6AhlxOYNnoAc9jhSAmNsMmJCteVVBV96c9jgeP9QOF2WtLnq6md8/uFocOelUc= =iUXk -----END PGP SIGNATURE-----
On Sun, 26 Oct 2014 17:16:46 +0200 s7r <s7r@sky-ip.org> wrote:
3. Last thing, the page https://bridges.torproject.org/ does not contain obfs4 in the drop-down list where the user needs to select the pluggable transport. It only allows requests for obfs2, obfs3, scramblesuit and fteproxy bridges. Don't know about fteproxy, but shouldn't obfs2 be deprecated or is it still working/used?
A note on this (I don't handle packaging, sorry). obfs4 propbably should be added to the dropdown once there is a critical mass of bridges in the database, and when obfs4 is in official Tor Browser builds. As far as I am aware, the official integration (as opposed to my obsolete not-really-working-anymore snapshots) is scheduled to happen in the next alpha series. Regarding obfs2, it still "works" in some environments if the DPI used by the censor is not particularly sophisticated (not targeted specifically at detecting obfs2). I personally think that it should be deprecated sooner rather than later, but others have disagreed with me on this. Hope that helps, -- Yawning Angel
s7r:
2. Configured some obfs4 bridges using obfs4proxy. They work very good, however it's a little bit complicated since package obfs4proxy exists in Debian sid, but not in deb.torproject.org, so you have to add sid repo to sources.list, install obfs4proxy and then make sure you edit apt preferences or comment the sid repo from the list in order not to upgrade you entire Debian system with packages from unstable/testing branch. Received couple of emails from users wanted to deploy obfs4 bridges and were confused.
Is it possible to include obfs4proxy in deb.torproject.org for Debian
You should now be able to get obfs4proxy by using: deb http://deb.torproject.org/torproject.org obfs4proxy main The package should work on most Ubuntu and Debian versions. It is available for amd64 and i386. -- Lunar <lunar@torproject.org>
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/26/2014 7:56 PM, Lunar wrote:
s7r:
2. Configured some obfs4 bridges using obfs4proxy. They work very good, however it's a little bit complicated since package obfs4proxy exists in Debian sid, but not in deb.torproject.org, so you have to add sid repo to sources.list, install obfs4proxy and then make sure you edit apt preferences or comment the sid repo from the list in order not to upgrade you entire Debian system with packages from unstable/testing branch. Received couple of emails from users wanted to deploy obfs4 bridges and were confused.
Is it possible to include obfs4proxy in deb.torproject.org for Debian
You should now be able to get obfs4proxy by using:
deb http://deb.torproject.org/torproject.org obfs4proxy main
The package should work on most Ubuntu and Debian versions. It is available for amd64 and i386.
Dear Lunar, Thank you! I can see the package in the main pool, but wanted to ask something: any reason why this is not available using: deb http://deb.torproject.org/torproject.org `$lsb_release -c` main Basically the same where Tor, tor-arm and obfsproxy are available too?
_______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJUTWraAAoJEIN/pSyBJlsRyZIH/iUNG37+60MBaqDw4RvEBaVW 5VUga+zBCCyBj9kxE8i9YUNdS4sLRWFkpLFP05d/mNpGpyxL9fvQqwbhwdcOaXCT SnyCQfYnRW52BVhLM0EsuHmjGmsU9gtY2ffr7JUR4rMbTLdT2HzgLVHQ6N6coZP0 Fcgbj3Xg9wSigKS2ZxXKdeaGtmMWrHKPHGR5NFVuL8XVTWTND0g66v2uzffBjRDe JMydIhVsckvipGHJa2Cw+T3VJZUKKLcDUv8q73TrVq1nAEGdhMeGmS7t2bFej5/2 dNTgjfx/EUuOwea7jQwH0T+tY9ImAS0HLrKaaDIIYa9tqwd+qL/zbcSivLOrp5o= =AkAO -----END PGP SIGNATURE-----
s7r:
Thank you! I can see the package in the main pool, but wanted to ask something: any reason why this is not available using: deb http://deb.torproject.org/torproject.org `$lsb_release -c` main
Basically the same where Tor, tor-arm and obfsproxy are available too?
Because obfs4proxy is in Go and statically linked. The same package can be used on many distributions. It could not be built on every suite though, as they don't have the needed build dependencies. -- Lunar <lunar@torproject.org>
participants (3)
-
Lunar -
s7r -
Yawning Angel