(no title)
tallytarik | 2 months ago
There are also other methods, like using zmap/zgrab to probe for servers that respond to VPN software handshakes, which can in theory be run against the entire IP space. (this also highlights non-commercial VPNs which are not generally the target of our detection, so we use this sparingly)
It will never cover every VPN or proxy in existence, but it gets pretty close.
acka|2 months ago
Assuming your VPN identification service operates commercially, I trust that you are in full compliance with all contractual agreements and Terms of Service for the services you utilize. Many of these agreements specifically prohibit commercial use, which could encompass the harvesting of exit node IP addresses and the subsequent sale of such information.
infecto|2 months ago
fourside|2 months ago
MangoToupe|2 months ago
Why? It's not like there's any real moral (or, likely, legal) reason to care beyond avoiding the service's ban hammer.
immibis|2 months ago
Unless you're the one-in-a-million unlucky user who gets prosecuted under the CFAA's very generic "unauthorized access to a protected computer" clause, like Aaron Swartz. It seems the general consensus is this doesn't apply to breaking a website ToS, and Aaron was only in so much trouble because he broke into a network closet, as well as for copyright violation. But consult a lawyer if unsure. (That's another difference: A business will ask a lawyer if it wants to do something shady, while an individual will simply avoid doing it)
addandsubtract|2 months ago
0xdeadbeefbabe|2 months ago
How does the buyer even know what the precision and recall rates might be?
recursive|2 months ago
ranger_danger|2 months ago
The legitimate end-user will then no longer be able to use e.g. SoundCloud.
blibble|2 months ago
rdsubhas|2 months ago
bombcar|2 months ago
You just track and block /24 or /16 as necessary.
tallytarik|2 months ago
Even with IPv6 it's not a huge problem. With a few samples we can know that a provider is operating in a given /64 or /48 or even /32 space, and can assign a confidence level that the range is used for VPNs.
tux3|2 months ago
vb-8448|2 months ago
kube-system|2 months ago
https://ip-ranges.amazonaws.com/ip-ranges.json
https://digitalocean.com/geo/google.csv
(And even if they don't publish them, you can just look up the ranges owned by any autonomous network with the appropriate registry.)
tallytarik|2 months ago
dizhn|2 months ago
unknown|2 months ago
[deleted]
unknown|2 months ago
[deleted]
m00dy|2 months ago
cons0le|2 months ago