From: Zac Medico <zmedico@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH v2] Support escaping network-sandbox through SOCKSv5 proxy
Date: Sun, 25 Jan 2015 13:47:38 -0800 [thread overview]
Message-ID: <54C5647A.7040305@gentoo.org> (raw)
In-Reply-To: <1422194414-31669-1-git-send-email-mgorny@gentoo.org>
On 01/25/2015 06:00 AM, Michał Górny wrote:
> diff --git a/bin/socks5-server.py b/bin/socks5-server.py
> new file mode 100644
> index 0000000..c079018
> --- /dev/null
> +++ b/bin/socks5-server.py
> @@ -0,0 +1,218 @@
> +#!/usr/bin/env python
> +# SOCKSv5 proxy server for network-sandbox
> +# Copyright 2015 Gentoo Foundation
> +# Distributed under the terms of the GNU General Public License v2
> +
> +import asyncore
> +import errno
> +import socket
> +import struct
> +import sys
> +
> +
> +class ProxyConnection(asyncore.dispatcher_with_send):
> + _addr = None
> + _connected = False
> + _family = socket.AF_INET
> + _proxy_conn = None
> +
> + def __init__(self, proxy_conn):
> + self._proxy_conn = proxy_conn
> + asyncore.dispatcher_with_send.__init__(self)
> + self.create_socket(self._family, socket.SOCK_STREAM)
> +
> + def start_connection(self, host, port):
> + try:
> + self.connect((host, port))
> + except:
> + self.handle_error()
> +
> + def handle_read(self):
> + buf = self.recv(4096)
> + self._proxy_conn.send(buf)
The self.recv calls should probably handle BlockingIOError, since the
docs say it can be raised "even though select.select() or select.poll()
has reported the socket ready for reading".
--
Thanks,
Zac
next prev parent reply other threads:[~2015-01-25 21:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-25 14:00 [gentoo-portage-dev] [PATCH v2] Support escaping network-sandbox through SOCKSv5 proxy Michał Górny
2015-01-25 21:43 ` Zac Medico
2015-01-25 22:01 ` Michał Górny
2015-01-25 21:47 ` Zac Medico [this message]
2015-01-25 21:58 ` Zac Medico
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54C5647A.7040305@gentoo.org \
--to=zmedico@gentoo.org \
--cc=gentoo-portage-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox