Man
Professional
- Messages
- 3,051
- Reaction score
- 577
- Points
- 113
Hello, my dear bank carder.
It is quite possible that you, like all of us once, read a couple of manuals, downloaded Dolphin-Ultra-Mega Antidetect with Free Sub and mentally prepared yourself for the fact that in 2 days you will turn your $200 into $10k. You bought a sock on LuxSox/Faceless/NSox/922 or some other piece of crap that sells this port to 300 people, stuck it in antidetect and went to make some money, but here's the problem. Your savings from school lunches floated away into the void, because absolutely nothing is registered/entered. So, you asked your mom for money, earned money at McDonald's or took out a microloan (depending on your age and financial habits) and are thinking about how to work so as not to screw up the whole cutlet again. But this is all poetry and the VCC regs ate it up. And we'll move on to the harsh theory, and after watching a couple of trash-vector videos we hear horror stories about udp, quic and other stories. So what to do with all these socks-VPNs in the end?
Let's start with the old, but not very kind Socks5. Why not very kind? Because it's a bastard, like your buddy who with red eyes gets caught by the cops that you have weight in your pocket, just like socks get caught by antifraud. Why? At the very least, they do not have their own UDP connection, through which (by default on port 53) DNS requests are sent. In general, this is fixed by redirecting DNS requests via HTTPS/TLS, which can be done on any Raspberry firmware presented on the market, as well as blocking QUIC (UDP port 443). Or in the firewall settings on Windows/Mac OS (on Mac it is solved in the command line, I think there is no point in describing it since it can really be googled - well, okay, I did it for you), but from experience such manipulations in the OS can sometimes cause technical problems with connections without DNS redirection. There are also Shadowsocks with partial encryption, which previously helped the Chinese bypass blocking, this is essentially the same fruit.
Next we have who. Wireguard. There is not much to say about it, this option is not suitable for work, firstly it is too heavy, secondly it cuts the connection speed so badly when using a weak client/server. But it is encrypted so much that you will up, so for those who are afraid of cyber trash at the door - it is the best thing to put it as the first link in the connection, fortunately it is very easy to install on the server via WG-Easy, from where it is downloaded in the web interface and installed on almost any modern router.
PPTP is an ancient piece of crap. It doesn't have a UDP connection, so you have to do exactly the same thing as with a sock, but in practice, broken residential PPTP is much better than socks. In short, if you have a Raspberry Pi or you send traffic through some Linux like a modified Whonix (how to do this - who the knows, maybe I'll get to similar solutions later, because this is extremely awesome) - it's quite viable. Just don't forget about redirecting DNS requests, otherwise it will leak.
Well, we are getting closer to what solves almost all our problems except for crooked hands. This is OpenVPN. In this whole list of fraudulent invalids, this is definitely our bro. Firstly, it doesn't give a shit about all these newfangled QUIC, because it has its own webrtc+udp. Secondly, it doesn't get detected like wg, and you can also use the OpenVPN+socks bundle if you are that unique vcc registrator who wants to save on registration, but to run the connection through the socks client is unacceptable for you, because it is technically illiterate and fraudulent. Well, in addition, it does not take as many resources as wireguard, so you can use resident configs on cracked routers. In short, I think you got the gist. By the way, you can check for DNS leaks on the website dnsleaktest.com, where ideally there should be provider DNS, Google's will occasionally work (since they are in 40% of used routers), or you can use dns 1.1.1.1 - cloudflare.
To all tight cash-outs and sleeping antifraud. Peace.
It is quite possible that you, like all of us once, read a couple of manuals, downloaded Dolphin-Ultra-Mega Antidetect with Free Sub and mentally prepared yourself for the fact that in 2 days you will turn your $200 into $10k. You bought a sock on LuxSox/Faceless/NSox/922 or some other piece of crap that sells this port to 300 people, stuck it in antidetect and went to make some money, but here's the problem. Your savings from school lunches floated away into the void, because absolutely nothing is registered/entered. So, you asked your mom for money, earned money at McDonald's or took out a microloan (depending on your age and financial habits) and are thinking about how to work so as not to screw up the whole cutlet again. But this is all poetry and the VCC regs ate it up. And we'll move on to the harsh theory, and after watching a couple of trash-vector videos we hear horror stories about udp, quic and other stories. So what to do with all these socks-VPNs in the end?
Let's start with the old, but not very kind Socks5. Why not very kind? Because it's a bastard, like your buddy who with red eyes gets caught by the cops that you have weight in your pocket, just like socks get caught by antifraud. Why? At the very least, they do not have their own UDP connection, through which (by default on port 53) DNS requests are sent. In general, this is fixed by redirecting DNS requests via HTTPS/TLS, which can be done on any Raspberry firmware presented on the market, as well as blocking QUIC (UDP port 443). Or in the firewall settings on Windows/Mac OS (on Mac it is solved in the command line, I think there is no point in describing it since it can really be googled - well, okay, I did it for you), but from experience such manipulations in the OS can sometimes cause technical problems with connections without DNS redirection. There are also Shadowsocks with partial encryption, which previously helped the Chinese bypass blocking, this is essentially the same fruit.
Next we have who. Wireguard. There is not much to say about it, this option is not suitable for work, firstly it is too heavy, secondly it cuts the connection speed so badly when using a weak client/server. But it is encrypted so much that you will up, so for those who are afraid of cyber trash at the door - it is the best thing to put it as the first link in the connection, fortunately it is very easy to install on the server via WG-Easy, from where it is downloaded in the web interface and installed on almost any modern router.
PPTP is an ancient piece of crap. It doesn't have a UDP connection, so you have to do exactly the same thing as with a sock, but in practice, broken residential PPTP is much better than socks. In short, if you have a Raspberry Pi or you send traffic through some Linux like a modified Whonix (how to do this - who the knows, maybe I'll get to similar solutions later, because this is extremely awesome) - it's quite viable. Just don't forget about redirecting DNS requests, otherwise it will leak.
Well, we are getting closer to what solves almost all our problems except for crooked hands. This is OpenVPN. In this whole list of fraudulent invalids, this is definitely our bro. Firstly, it doesn't give a shit about all these newfangled QUIC, because it has its own webrtc+udp. Secondly, it doesn't get detected like wg, and you can also use the OpenVPN+socks bundle if you are that unique vcc registrator who wants to save on registration, but to run the connection through the socks client is unacceptable for you, because it is technically illiterate and fraudulent. Well, in addition, it does not take as many resources as wireguard, so you can use resident configs on cracked routers. In short, I think you got the gist. By the way, you can check for DNS leaks on the website dnsleaktest.com, where ideally there should be provider DNS, Google's will occasionally work (since they are in 40% of used routers), or you can use dns 1.1.1.1 - cloudflare.
To all tight cash-outs and sleeping antifraud. Peace.
