>From my perspective SOCKS should be implemented in third-party library. If the library need to install own DNS lookup -- that's ok. Please take a look on https://code.google.com/p/tulip/issues/detail?id=160 But personally I don't like to include SOCKS into asyncio itself.
On Wed, Jun 11, 2014 at 3:01 AM, MaddinW1993 <[email protected]> wrote: > Hello people, > > I ask for SOCKS proxy support to be included into asyncio. The goal would be > to route both DNS queries as well as actual network requests through the > socks proxy listening on a local port. As of now, it appears to me that it > is forbiddingly difficult to do that through extending asyncio and not > replacing great parts of the underlying code. DNS lookups are being cached > and open on a regular socket regardless, even when a socket which was > already connected to the SOCKS was passed to the loop.create_connection > method. If a user minds his privacy and uses tor, this is likely against his > will as an adversary could learn about visited sites that way. The only > possibility I could find is by monkeypatching the > base_events._check_already_resolved method, and I think think there should > be a more beautiful way to do this in Python. > > Thank you for your consideration. > > -- Thanks, Andrew Svetlov
