<feed xmlns='http://www.w3.org/2005/Atom'>
<title>user/yawning/obfsproxy, branch bug11558</title>
<subtitle>Yawning's Python pluggable transport proxy repository</subtitle>
<link rel='alternate' type='text/html' href='https://gitweb.torproject.org/user/yawning/obfsproxy.git/'/>
<entry>
<title>Change zope usage to deal with really old zope.</title>
<updated>2014-04-22T21:02:09+00:00</updated>
<author>
<name>Yawning Angel</name>
<email>yawning@torproject.org</email>
</author>
<published>2014-04-22T21:02:09+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.torproject.org/user/yawning/obfsproxy.git/commit/?id=ec82774a4fb44ca9a7e08be3013ace062554e600'/>
<id>ec82774a4fb44ca9a7e08be3013ace062554e600</id>
<content type='text'>
Debian squeeze packages zope.interface-3.5.3, which is utterly
prehistoric and was puking on the `@implementer` decorator.  Fixing
this makes the code work, though txsocksx also has a dependency on
"zope.interface that isn't from 2009".
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Debian squeeze packages zope.interface-3.5.3, which is utterly
prehistoric and was puking on the `@implementer` decorator.  Fixing
this makes the code work, though txsocksx also has a dependency on
"zope.interface that isn't from 2009".
</pre>
</div>
</content>
</entry>
<entry>
<title>Add compatibility code for old versions of Twisted.</title>
<updated>2014-04-19T05:09:20+00:00</updated>
<author>
<name>Yawning Angel</name>
<email>yawning@torproject.org</email>
</author>
<published>2014-04-19T05:09:20+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.torproject.org/user/yawning/obfsproxy.git/commit/?id=3858f38cc8379ea46a69da60e3d5fafc14024240'/>
<id>3858f38cc8379ea46a69da60e3d5fafc14024240</id>
<content type='text'>
Recent changes has broken obfsproxy on systems running Twisted &lt; 13.2.0.
We now monkeypatch Twisted from __init__.py if the new features we are
expected are missing.

Things added:

 * twisted.internet.error.UnsupportedAddressFamily - Just a
   `Exception`, 100% compatible with Twisted.

 * twisted.internet.endpoints.HostnameEndpoint - The older the copy of
   Twisted is, the bigger the difference between the real
   implementation.

    * IPv4 will always work.
    * IPv6 will work for Twisted &gt;= 12.2.0.
    * Hostname (DNS resolution) will never work.

  The limitations here are ok, since the endpoint in question is used
  when tunneling obfsproxy traffic through another proxy, and tor will
  configure that via IP address.

This fixes bug #11558.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Recent changes has broken obfsproxy on systems running Twisted &lt; 13.2.0.
We now monkeypatch Twisted from __init__.py if the new features we are
expected are missing.

Things added:

 * twisted.internet.error.UnsupportedAddressFamily - Just a
   `Exception`, 100% compatible with Twisted.

 * twisted.internet.endpoints.HostnameEndpoint - The older the copy of
   Twisted is, the bigger the difference between the real
   implementation.

    * IPv4 will always work.
    * IPv6 will work for Twisted &gt;= 12.2.0.
    * Hostname (DNS resolution) will never work.

  The limitations here are ok, since the endpoint in question is used
  when tunneling obfsproxy traffic through another proxy, and tor will
  configure that via IP address.

This fixes bug #11558.
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge branch 'bug8956_tweak'</title>
<updated>2014-04-16T13:31:35+00:00</updated>
<author>
<name>George Kadianakis</name>
<email>desnacked@riseup.net</email>
</author>
<published>2014-04-16T13:31:35+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.torproject.org/user/yawning/obfsproxy.git/commit/?id=e7c4294ee4965f6bd4f5d3edd7c28d3d9cb0f582'/>
<id>e7c4294ee4965f6bd4f5d3edd7c28d3d9cb0f582</id>
<content type='text'>
Conflicts:
	ChangeLog
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Conflicts:
	ChangeLog
</pre>
</div>
</content>
</entry>
<entry>
<title>Tweak the proxy logging a bit.</title>
<updated>2014-04-16T13:10:13+00:00</updated>
<author>
<name>George Kadianakis</name>
<email>desnacked@riseup.net</email>
</author>
<published>2014-04-16T13:10:13+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.torproject.org/user/yawning/obfsproxy.git/commit/?id=a2dc745745e5a827fc29a8c474268cc014c08aba'/>
<id>a2dc745745e5a827fc29a8c474268cc014c08aba</id>
<content type='text'>
Clean some long lines, and some instances of pylint's
logging-not-lazy (although the rest of the codebase has many more
instances of this).
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Clean some long lines, and some instances of pylint's
logging-not-lazy (although the rest of the codebase has many more
instances of this).
</pre>
</div>
</content>
</entry>
<entry>
<title>Clean up error handling when the http proxy doesn't return status.</title>
<updated>2014-04-16T08:41:42+00:00</updated>
<author>
<name>Yawning Angel</name>
<email>yawning@torproject.org</email>
</author>
<published>2014-04-16T08:41:42+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.torproject.org/user/yawning/obfsproxy.git/commit/?id=a79b8ae6a147fdebc59e6555ad5e985487c47f94'/>
<id>a79b8ae6a147fdebc59e6555ad5e985487c47f94</id>
<content type='text'>
Some HTTP proxys opt to close the connection instead of returning a
HTTP status code on certain failures (Eg: polipo auth faliure, privoxy
ACL denial).  This change logs a better error message to the obfsproxy
log when that happens.

As an added bonus the SOCKS5 server now knows about EHOSTUNREACH, so
a more informative response is sent on that failure type.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Some HTTP proxys opt to close the connection instead of returning a
HTTP status code on certain failures (Eg: polipo auth faliure, privoxy
ACL denial).  This change logs a better error message to the obfsproxy
log when that happens.

As an added bonus the SOCKS5 server now knows about EHOSTUNREACH, so
a more informative response is sent on that failure type.
</pre>
</div>
</content>
</entry>
<entry>
<title>Don't feed None to parseProxyURI() in external mode.</title>
<updated>2014-04-15T12:44:51+00:00</updated>
<author>
<name>George Kadianakis</name>
<email>desnacked@riseup.net</email>
</author>
<published>2014-04-15T12:44:51+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.torproject.org/user/yawning/obfsproxy.git/commit/?id=2476e260aacaa7696ed2393679d5244971dcca0c'/>
<id>2476e260aacaa7696ed2393679d5244971dcca0c</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Add support for connecting via a HTTPS CONNECT proxy.</title>
<updated>2014-04-15T10:00:21+00:00</updated>
<author>
<name>Yawning Angel</name>
<email>yawning@torproject.org</email>
</author>
<published>2014-04-15T10:00:21+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.torproject.org/user/yawning/obfsproxy.git/commit/?id=2477925050651940a40741b2c12910bb36250594'/>
<id>2477925050651940a40741b2c12910bb36250594</id>
<content type='text'>
This adds a HTTPS CONNECT client.  It's been lightly tested with both
privoxy and apache2 and appears to work, both without authentication
and with Basic.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This adds a HTTPS CONNECT client.  It's been lightly tested with both
privoxy and apache2 and appears to work, both without authentication
and with Basic.
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix connecting via a SOCKS proxy.</title>
<updated>2014-04-15T01:08:58+00:00</updated>
<author>
<name>Yawning Angel</name>
<email>yawning@torproject.org</email>
</author>
<published>2014-04-15T01:08:58+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.torproject.org/user/yawning/obfsproxy.git/commit/?id=58326981ebfa2fbfffa76a1880e7bfec4633301f'/>
<id>58326981ebfa2fbfffa76a1880e7bfec4633301f</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Add ChangeLog entry for #11190.</title>
<updated>2014-04-13T11:27:05+00:00</updated>
<author>
<name>George Kadianakis</name>
<email>desnacked@riseup.net</email>
</author>
<published>2014-04-13T11:27:05+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.torproject.org/user/yawning/obfsproxy.git/commit/?id=b58fd9e1ef264796b6bddbde5db117472fb674a0'/>
<id>b58fd9e1ef264796b6bddbde5db117472fb674a0</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Changed the obfsproxy shebang to point to `python2`</title>
<updated>2014-04-13T11:21:58+00:00</updated>
<author>
<name>Yawning Angel</name>
<email>yawning@torproject.org</email>
</author>
<published>2014-04-11T23:27:06+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.torproject.org/user/yawning/obfsproxy.git/commit/?id=2d9d4da6e53e809d4d2ae584a34e0d1c57575140'/>
<id>2d9d4da6e53e809d4d2ae584a34e0d1c57575140</id>
<content type='text'>
On all the systems I've checked so far running a U*IX variant,
`python2` is a valid symlink to the Python 2.x.x interpreter.  Since
certain systems are also shipping Python 3 and some make it the default
system python, the shebang should be explicit.

This fixes bug #11190.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
On all the systems I've checked so far running a U*IX variant,
`python2` is a valid symlink to the Python 2.x.x interpreter.  Since
certain systems are also shipping Python 3 and some make it the default
system python, the shebang should be explicit.

This fixes bug #11190.
</pre>
</div>
</content>
</entry>
</feed>
