[Pkg-privacy-commits] [obfsproxy] 123/353: Initial Debian packaging

Ximin Luo infinity0 at moszumanska.debian.org
Sat Aug 22 13:01:49 UTC 2015


This is an automated email from the git hooks/post-receive script.

infinity0 pushed a commit to branch master
in repository obfsproxy.

commit 736042775767384dbdeebc01e7f97fe2db69770e
Author: Jérémy Bobbio <lunar at debian.org>
Date:   Wed Feb 6 17:04:43 2013 +0100

    Initial Debian packaging
    
    Closes: #699922
---
 debian/README.Debian        |  73 ++++++++++++++++++++++++
 debian/README.source        |  22 +++++++
 debian/changelog            |   5 ++
 debian/compat               |   1 +
 debian/control              |  34 +++++++++++
 debian/copyright            |  44 ++++++++++++++
 debian/gbp.conf             |   2 +
 debian/pyobfsproxy.1.txt    | 136 ++++++++++++++++++++++++++++++++++++++++++++
 debian/pyobfsproxy.docs     |   3 +
 debian/pyobfsproxy.manpages |   1 +
 debian/rules                |  13 +++++
 debian/source/format        |   1 +
 12 files changed, 335 insertions(+)

diff --git a/debian/README.Debian b/debian/README.Debian
new file mode 100644
index 0000000..2ff39eb
--- /dev/null
+++ b/debian/README.Debian
@@ -0,0 +1,73 @@
+pyobfsproxy for Debian
+======================
+
+Configuring an obfs2/obfs3 bridge
+---------------------------------
+
+(Inspired by upstream HOWTO.txt)
+
+This is a short guide on how to setup a pyobfsproxy obfs2/obfs3 bridge:
+
+1. Setup Tor
+
+   Edit /etc/tor/torrc to add:
+
+       SocksPort 0
+       ORPort 443 # or some other port if you already run a webserver/skype
+       BridgeRelay 1
+       Exitpolicy reject *:*
+
+       ## CHANGEME_1 -> provide a nickname for your bridge, can be anything you like
+       #Nickname CHANGEME_1
+       ## CHANGEME_2 -> provide some email address so we can contact you if there's a problem
+       #ContactInfo CHANGEME_2
+
+       ServerTransportPlugin obfs2,obfs3 exec /usr/bin/pyobfsproxy managed
+
+   Don't forget to uncomment and edit the CHANGEME fields.
+
+2. Launch Tor and verify that it bootstraps
+
+   Restart Tor to use the new configuration file:
+
+       # service tor restart
+
+   Now check /var/log/tor/log and you should see something like this:
+
+       Nov 05 16:40:45.000 [notice] We now have enough directory information to build circuits.
+       Nov 05 16:40:45.000 [notice] Bootstrapped 80%: Connecting to the Tor network.
+       Nov 05 16:40:46.000 [notice] Bootstrapped 85%: Finishing handshake with first hop.
+       Nov 05 16:40:46.000 [notice] Bootstrapped 90%: Establishing a Tor circuit.
+       Nov 05 16:40:48.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
+       Nov 05 16:40:48.000 [notice] Bootstrapped 100%: Done.
+
+   If Tor is earlier in the bootstrapping phase, wait until it gets to 100%.
+
+3. Configure the firewall if needed
+
+   If you're behind a NAT/firewall, you'll need to make your bridge
+   reachable from the outside world — both on the ORPort and the
+   obfsproxy port. The ORPort is whatever you defined in step two
+   above. To find your obfsproxy port, check your Tor logs for two
+   lines similar to these:
+
+       Oct 05 20:00:41.000 [notice] Registered server transport 'obfs2' at '0.0.0.0:26821
+       Oct 05 20:00:42.000 [notice] Registered server transport 'obfs3' at '0.0.0.0:40172
+
+   The last number in each line, in this case 26821 and 40172, are the
+   TCP port numbers that you need to forward through your
+   firewall. (This port is randomly chosen the first time Tor starts,
+   but Tor will cache and reuse the same number in future runs.) If you
+   want to change the number, use Tor 0.2.4.7-alpha or later, and set
+   "ServerTransportListenAddr obfs2 0.0.0.0:26821" in your torrc.
+
+Using an obfs3 bridge
+---------------------
+
+To use an obfs3, please add the following lines to /etc/tor/torrc:
+
+    ClientTransportPlugin obfs2,obfs3 exec /usr/bin/pyobfsproxy managed
+    UseBridges 1
+    Bridge obfs3 192.0.2.42:443 C2A9DC82AA7E85DB6465EC8C4B1B4B1B77787BE0
+
+Adjust address, port and the optional fingerprint accordingly.
diff --git a/debian/README.source b/debian/README.source
new file mode 100644
index 0000000..a50aa66
--- /dev/null
+++ b/debian/README.source
@@ -0,0 +1,22 @@
+README.source for the pyobfsproxy package
+=========================================
+
+pyobfsproxy is managed in a Git repository using git-buildpackage.
+
+Upstream tarballs are imported using git-import-orig with:
+
+ * `--pristine-tar` to record upstream tarball,
+ * `--upstream-vcs-tag` to link upstream source repository.
+
+Quilt patches are managed using gbp-pq.
+
+Packaging practices also follow most of the advices provided by Russ
+Allbery at: <http://www.eyrie.org/~eagle/notes/debian/git.html>
+
+The branches are organized as follow:
+
+  * upstream: tracks the "master" branch of upstream repository [1]
+  * patch-queue/*: branches exported to quilt patches (handled by gbp-pq)
+  * master: export of patch-queue/* branches and Debian specific changes
+
+[1] <https://git.torproject.org/pluggable-transports/pyobfsproxy.git>
diff --git a/debian/changelog b/debian/changelog
new file mode 100644
index 0000000..90e5ef0
--- /dev/null
+++ b/debian/changelog
@@ -0,0 +1,5 @@
+pyobfsproxy (0.0.2-1) UNRELEASED; urgency=low
+
+  * Initial release. (Closes: #699922)
+
+ -- Jérémy Bobbio <lunar at debian.org>  Wed, 06 Feb 2013 14:42:54 +0100
diff --git a/debian/compat b/debian/compat
new file mode 100644
index 0000000..45a4fb7
--- /dev/null
+++ b/debian/compat
@@ -0,0 +1 @@
+8
diff --git a/debian/control b/debian/control
new file mode 100644
index 0000000..0e1a894
--- /dev/null
+++ b/debian/control
@@ -0,0 +1,34 @@
+Source: pyobfsproxy
+Maintainer: Jérémy Bobbio <lunar at debian.org>
+Section: python
+Priority: extra
+Build-Depends: asciidoc,
+               debhelper (>= 8),
+               docbook-xsl,
+               python-crypto,
+               python-setuptools,
+               python-twisted-core,
+               xsltproc
+Standards-Version: 3.9.4
+X-Python-Version: >= 2.7
+Vcs-Git: git://anonscm.debian.org/collab-maint/pyobfsproxy.git
+Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/pyobfsproxy.git
+
+Package: pyobfsproxy
+Architecture: all
+Depends: python,
+         python-argparse,
+         python-crypto,
+         python-pyptlib,
+         python-twisted-core,
+         tor (>= 0.2.4),
+         ${misc:Depends},
+         ${python:Depends}
+Description: pluggable transport proxy for Tor (Python implementation)
+ pyobfsproxy is a tool that attempts to circumvent censorship by
+ transforming the Tor traffic between the client and the bridge. This way
+ censors, who usually monitor traffic between the client and the bridge, will
+ see innocent-looking transformed traffic instead of the actual Tor traffic.
+ .
+ It is written in Python and is compliant with the Tor pluggable transports
+ specification.
diff --git a/debian/copyright b/debian/copyright
new file mode 100644
index 0000000..4dd2aa8
--- /dev/null
+++ b/debian/copyright
@@ -0,0 +1,44 @@
+Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Upstream-Name: pyobfsproxy
+Upstream-Contact: George Kadianakis <desnacked at riseup.net>
+Source: https://git.torproject.org/pluggable-transports/pyobfsproxy.git
+
+Files: *
+Copyright: Copyright 2012      Brandon Wiley <brandon at blanu.net>
+           Copyright 2012-2013 George Kadianakis <desnacked at riseup.net>
+License: BSD-3-clause
+ Redistribution and use in source and binary forms, with or without
+ modification, are permitted provided that the following conditions are
+ met:
+ .
+    * Redistributions of source code must retain the above copyright
+      notice, this list of conditions and the following disclaimer.
+ .
+    * Redistributions in binary form must reproduce the above copyright
+      notice, this list of conditions and the following disclaimer in
+      the documentation and/or other materials provided with the
+      distribution.
+ .
+    * Neither the names of the copyright owners nor the names of its
+      contributors may be used to endorse or promote products derived
+      from this software without specific prior written permission.
+ .
+ THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
+ IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
+ TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
+ PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
+ OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+ SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+ LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+ DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+ THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+ (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+ OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+Files: debian/*
+Copyright: Copyright 2013 Jérémy Bobbio <lunar at debian.org>
+License: permissive
+ Copying and distribution of this package, with or without
+ modification, are permitted in any medium without royalty
+ provided the copyright notice and this notice are
+ preserved.
diff --git a/debian/gbp.conf b/debian/gbp.conf
new file mode 100644
index 0000000..70d997b
--- /dev/null
+++ b/debian/gbp.conf
@@ -0,0 +1,2 @@
+[git-import-orig]
+pristine-tar = False
diff --git a/debian/pyobfsproxy.1.txt b/debian/pyobfsproxy.1.txt
new file mode 100644
index 0000000..9ebd0d3
--- /dev/null
+++ b/debian/pyobfsproxy.1.txt
@@ -0,0 +1,136 @@
+PYOBFSPROXY(1)
+==============
+:doctype: manpage
+
+
+NAME
+----
+pyobfsproxy - a pluggable transports proxy
+
+
+SYNOPSIS
+--------
+pyobfsproxy [--log-file 'log_file']
+            [--log-min-severity 'severity'] [--no-log]
+            [--no-safe-logging]
+            managed
+pyobfsproxy [--log-file 'log_file']
+            [--log-min-severity 'severity'] [--no-log]
+            [--no-safe-logging]
+            'transport'
+            [-h] [--dest 'dest']
+            [--ext-cookie-file 'ext_cookie_file'] ...
+            'mode' 'listen_addr'
+pyobfsproxy --help
+
+
+
+DESCRIPTION
+-----------
+*pyobfsproxy* is a tool that attempts to circumvent censorship, by transforming
+the Tor traffic between the client and the bridge. This way, censors, who
+usually monitor traffic between the client and the bridge, will see
+innocent-looking transformed traffic instead of the actual Tor traffic.
+
+
+OPTIONS
+-------
+**--log-file** 'log_file'::
+     Set logfile location.
+**--log-min-severity** 'severity'::
+     Set minimum logging severity (default: no logging). 'severity' must be
+     one of *error*, *warning*, *info*, *debug*.
+**--no-log**::
+     Disable logging.
+**--no-safe-logging**::
+     Disable safe (scrubbed address) logging.
+**-h, --help**::
+     Show help message and exit.
+
+
+MANAGED TRANSPORT
+-----------------
+
+Using *managed* as 'TRANSPORT' allows Tor to start and control pyobfsproxy by
+itself. Add a line like the following to torrc to use it when acting as a
+bridge:
+
+     ServerTransportPlugin obfs2,obfs3 exec /usr/bin/pyobfsproxy managed
+
+When connecting to an obfuscated bridge, adapt the following:
+
+     ClientTransportPlugin obfs2,obfs3 exec /usr/bin/pyobfsproxy managed
+
+DUMMY TRANSPORT
+---------------
+Use a protocol that simply proxies data without obfuscating them. For tests only.
+
+No extra options.
+
+
+B64 TRANSPORT
+-------------
+Use a protocol that encodes data with *base64* before pushing them to the
+network.
+
+No extra options.
+
+
+OBFS2 TRANSPORT
+---------------
+Use the *obfs2* protocol. See
+<https://gitweb.torproject.org/obfsproxy.git/blob/HEAD:/doc/obfs2/protocol-spec.txt>
+for the specification.
+
+No extra options.
+
+
+OBFS3 TRANSPORT
+---------------
+Use the *obfs3* protocol. See
+<https://gitweb.torproject.org/pluggable-transports/pyobfsproxy.git/blob/HEAD:/doc/obfs3/obfs3-protocol-spec.txt>
+for the specification.
+
+No extra options.
+
+
+COMMON TRANSPORT OPTIONS
+------------------------
+
+Here's the common synopsis:
+
+
+Options common for all transports:
+
+**transport**::
+     One of *managed*, *dummy*, *b64*, *obfs2* or *obfs3*. See above for
+     details.
+
+*-h*::
+     Show help message and exit.
+
+**--dest** 'dest'::
+     Set destination address. Mandatory in all modes except *socks*.
+
+**--ext-cookie-file** 'ext_cookie_file'::
+     Configure the filesystem path where the Extended ORPort authentication
+     cookie is stored.
+
+**mode**::
+     Mode must be one of *server* (old-style ServerTransportPlugin),
+     *ext_server* (support for Extended ORPort), *client* (bridge client) or
+     *socks* (client using SOCKS to connect to bridges).
+
+**listen_addr**::
+     Address on which the proxy will listen.
+
+
+BUGS
+----
+Plenty, probably. *pyobfsproxy* is still in development. Please report them.
+
+
+AUTHOR
+------
+George Kadianakis <asn at torproject.org>
+Brandon Wiley <brandon at blanu.net>
diff --git a/debian/pyobfsproxy.docs b/debian/pyobfsproxy.docs
new file mode 100644
index 0000000..985b580
--- /dev/null
+++ b/debian/pyobfsproxy.docs
@@ -0,0 +1,3 @@
+README
+doc/obfs3/obfs3-protocol-spec.txt
+doc/obfs3/obfs3-threat-model.txt
diff --git a/debian/pyobfsproxy.manpages b/debian/pyobfsproxy.manpages
new file mode 100644
index 0000000..87982ab
--- /dev/null
+++ b/debian/pyobfsproxy.manpages
@@ -0,0 +1 @@
+debian/pyobfsproxy.1
diff --git a/debian/rules b/debian/rules
new file mode 100755
index 0000000..ee02b5b
--- /dev/null
+++ b/debian/rules
@@ -0,0 +1,13 @@
+#!/usr/bin/make -f
+
+%:
+	dh $@ --buildsystem=python_distutils
+
+override_dh_installman:
+	a2x --no-xmllint --doctype manpage --format manpage debian/pyobfsproxy.1.txt
+	dh_installman -O--buildsystem=python_distutils
+
+ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
+override_dh_auto_test:
+	trial obfsproxy
+endif
diff --git a/debian/source/format b/debian/source/format
new file mode 100644
index 0000000..163aaf8
--- /dev/null
+++ b/debian/source/format
@@ -0,0 +1 @@
+3.0 (quilt)

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-privacy/packages/obfsproxy.git



More information about the Pkg-privacy-commits mailing list