4 ms·

I presume that they'd never get reused. And yes, there could be blocking by ranges. And while I doubt that Tor would ever do it, one could use residential IPs

I presume that they'd never get reused. And yes, there could be blocking by ranges. And while I doubt that Tor would ever do it, one could use residential IPs via "free" smartphone apps. Some VPN services may be doing that.

tjoff 7y ago
They are all listed... https://blog.torproject.org/changes-tor-exit-list-service https://blog.torproject.org/changes-tor-exit-list-service No one could not use residential IPs that way.
- mirimir 7y ago
  Yes, they're all listed now. But I don't see anything in https://trac.torproject.org/projects/tor/ticket/26646 https://trac.torproject.org/projects/tor/ticket/26646 about listing the IPv6 addresses. And using random addresses from multiple /48, that'd be an extremely long list. I was wrong about not reusing IPv6. But even so, using the same IPv6 would be very rare, given the number available. You say that no one could use residential IPs that way. But I know for a fact that it's already being done. For example, see https://luminati.io/proxy-networks/residential-ips https://luminati.io/proxy-networks/residential-ips.
  - throwaway2048 7y ago
    tor does not use ipv6 currently.
    - mirimir 7y ago
      Huh? https://metrics.torproject.org/rs.html#search/2001 https://metrics.torproject.org/rs.html#search/2001: I see 377 starting with 2001:.
      - deleted 7y ago
        [deleted]
  - tjoff 7y ago
    Why wouldn't they? Handful of blocked ranges yes... It's obvious that this isn't a goal of Tor.
    - mirimir 7y ago
      I'd say that it hasn't been Tor's goal. But blocking has become so common that user pressure to prevent it can no longer be ignored. If they don't act, they risk being replaced. I typically get around it by routing a VPN service, or a private VPN, through Tor. That also enables apps that require UDP. There is the risk of deanonymization, if VPN connections last too long and pin Tor circuits. Or if users don't adequately anonymize payment for VPN services or VPS used for private VPNs. I started playing with a set of bash scripts that creates multiple VPN connections, with each using a different Tor circuit, and tests them. It periodically switches from one to another, and kills the old one. So both Tor circuit and VPN exit IPv4 change periodically. A script ongoingly starts and tests new VPN connections, to maintain availability. It's basically a crude hack of Tor's approach to circuit management.

tjoff 7y ago

They are all listed... https://blog.torproject.org/changes-tor-exit-list-service https://blog.torproject.org/changes-tor-exit-list-service No one could not use residential IPs that way.

mirimir 7y ago
Yes, they're all listed now. But I don't see anything in https://trac.torproject.org/projects/tor/ticket/26646 https://trac.torproject.org/projects/tor/ticket/26646 about listing the IPv6 addresses. And using random addresses from multiple /48, that'd be an extremely long list. I was wrong about not reusing IPv6. But even so, using the same IPv6 would be very rare, given the number available. You say that no one could use residential IPs that way. But I know for a fact that it's already being done. For example, see https://luminati.io/proxy-networks/residential-ips https://luminati.io/proxy-networks/residential-ips.
- throwaway2048 7y ago
  tor does not use ipv6 currently.
  - mirimir 7y ago
    Huh? https://metrics.torproject.org/rs.html#search/2001 https://metrics.torproject.org/rs.html#search/2001: I see 377 starting with 2001:.
    - deleted 7y ago
      [deleted]
- tjoff 7y ago
  Why wouldn't they? Handful of blocked ranges yes... It's obvious that this isn't a goal of Tor.
  - mirimir 7y ago
    I'd say that it hasn't been Tor's goal. But blocking has become so common that user pressure to prevent it can no longer be ignored. If they don't act, they risk being replaced. I typically get around it by routing a VPN service, or a private VPN, through Tor. That also enables apps that require UDP. There is the risk of deanonymization, if VPN connections last too long and pin Tor circuits. Or if users don't adequately anonymize payment for VPN services or VPS used for private VPNs. I started playing with a set of bash scripts that creates multiple VPN connections, with each using a different Tor circuit, and tests them. It periodically switches from one to another, and kills the old one. So both Tor circuit and VPN exit IPv4 change periodically. A script ongoingly starts and tests new VPN connections, to maintain availability. It's basically a crude hack of Tor's approach to circuit management.