[Bug 1975416] [NEW] Torsocks fails to resolve domain names where ɪᴘv6 is available.

empty 1975416 at bugs.launchpad.net
Sun May 22 13:57:44 UTC 2022


Public bug reported:

simple step to reproduce :

$ torify wget https://rpc.ethermine.org
--2022-05-22 13:08:03--  https://rpc.ethermine.org/
Resolving rpc.ethermine.org (rpc.ethermine.org)... 1653217683 ERROR torsocks[669]: [socks5] Resolve destination buffer too small (in socks5_recv_resolve_reply() at socks5.c:701)
failed: Non-recoverable failure in name resolution.
wget: unable to resolve host address 'rpc.ethermine.org'

Where the buffer is too small because the first returned address is longer than with ɪᴘv4. Disabling ɪᴘv6 doesn’t work because the issue happens at name resolution (where the returned ɪᴘv6 addresses are normally ignored).
Of course, wget supports socks proxies, but many python packages like WebSockets or aiohttp or web3py don’t and thus have to rely on torsocks for using tor. So there’s no workarounds.

The problem is today ɪᴘv6 is far more available than it used to be… Not only do some websites like Google or Wikipedia provide ɪᴘv6 but many providers like Cloudflare provide ɪᴘv6 to all their protected websites.
As a result, this prevents using torsocks with most of the web and might even make torsocks completely unusable in the future.

I’m reporting it here as that specific part of the project seems to
abandonware upstream.

** Affects: python-websockets (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: torsocks (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: websocket-client (Ubuntu)
     Importance: Undecided
         Status: New

** Also affects: websocket-client (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: python-websockets (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to websocket-client in Ubuntu.
https://bugs.launchpad.net/bugs/1975416

Title:
  Torsocks fails to resolve domain names where ɪᴘv6 is available.

Status in python-websockets package in Ubuntu:
  New
Status in torsocks package in Ubuntu:
  New
Status in websocket-client package in Ubuntu:
  New

Bug description:
  simple step to reproduce :

  $ torify wget https://rpc.ethermine.org
  --2022-05-22 13:08:03--  https://rpc.ethermine.org/
  Resolving rpc.ethermine.org (rpc.ethermine.org)... 1653217683 ERROR torsocks[669]: [socks5] Resolve destination buffer too small (in socks5_recv_resolve_reply() at socks5.c:701)
  failed: Non-recoverable failure in name resolution.
  wget: unable to resolve host address 'rpc.ethermine.org'

  Where the buffer is too small because the first returned address is longer than with ɪᴘv4. Disabling ɪᴘv6 doesn’t work because the issue happens at name resolution (where the returned ɪᴘv6 addresses are normally ignored).
  Of course, wget supports socks proxies, but many python packages like WebSockets or aiohttp or web3py don’t and thus have to rely on torsocks for using tor. So there’s no workarounds.

  The problem is today ɪᴘv6 is far more available than it used to be… Not only do some websites like Google or Wikipedia provide ɪᴘv6 but many providers like Cloudflare provide ɪᴘv6 to all their protected websites.
  As a result, this prevents using torsocks with most of the web and might even make torsocks completely unusable in the future.

  I’m reporting it here as that specific part of the project seems to
  abandonware upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-websockets/+bug/1975416/+subscriptions




More information about the Ubuntu-openstack-bugs mailing list