How to use tor over an RDP without being blocked? : OpSec | Torhoo darknet markets
I was thinking of connecting to an RDP via tor to ensure my identity isn't exposed but it appears like I get blocked and I have attempted to use proxies obviously tor first and proxies second so the proxies don't know my IP but it appears like the proxies deny my tor connections as do the RDP servers so what should I do I don't really know anything too too advanced.
Tor does not easily support UDP which is what RDP uses msotly. Tor is mostly TCP based and there are some ways to make it work it is so slow you will not find value in it.
You might have some value in a browser based vnc connection which some providers allow and you can install yourself. You will have the same issue that it is slow and probably will disconnect constantly. You are probably blocked because of the provider or because of the exit node.
rdp is primarily tcp and udp secondary works fine with tor in most cases
i think the problem is with the proxies
preconfigured vnc is bad idea because who knows how they configured encryption he will leak everything to tor exit node
vnc should be set up manually from terminal
That is a lot of latency for a UDP connection, with or with not proxies.
You are right that by default the preconfigure vnc is not encrypted and would have to be manually encrypted. Web based RDP is an option but is slower than a regular rdp client. I think at the end adding a proxy is not necessary and he can make RDP work with tor but I would be suspicious that it does not leak information or go around the tor routing if not using something like tails or whonix.
If you're trying to use Tor over RDP and running into issues with being blocked, here's a more practical breakdown:
1. RDP Servers Blocking Tor Traffic
RDP servers often block Tor traffic due to the fact that many Tor exit nodes are flagged as suspicious or associated with malicious activity. So, they’ll prevent connections coming from these nodes.
2. Proxy Setup
You can try using proxies in addition to Tor. The typical setup might be:
Tor → Proxy → RDP Server
Here, Tor hides your real IP, the proxy hides the fact that you’re using Tor, and then you connect to the RDP server.
However, many proxies can detect and block Tor traffic too, especially if you're using standard datacenter proxies. Residential proxies tend to be less likely to be flagged because they look like they're coming from regular users (not datacenters).
3. Use Residential Proxies
If you're not already, residential proxies are the way to go. These are less likely to get blocked by the RDP server or any intermediary proxy service. They appear as if they’re coming from normal residential ISPs and not suspicious data centers, which is why they're harder to block.
4. Geo-blocking
Check whether the RDP server has any geographical restrictions (like IP geofencing) or blocks specific IP types (like Tor exit nodes or datacenter IPs). If you can control the RDP setup, try to disable these restrictions or use a proxy that hides your real location.
5. Reroute Your Exit Node
Sometimes Tor's exit nodes can get flagged and blocked. You can force Tor to use different exit nodes by editing the torrc file and specifying a different exit policy, or just restart Tor to get a new exit node. This might bypass the block, especially if the exit node you're using is on a blacklist.
6. Avoid DNS and WebRTC Leaks
Even if you are using Tor + proxy setup, make sure you're not leaking any identifying information. DNS leaks and WebRTC leaks can expose your real IP even if you're using Tor. Use tools to check for these leaks and ensure they’re fixed.
7. Obfuscated Tor Traffic
If your setup is still getting blocked, you can try obfuscating Tor traffic. Tools like obfs4 or meek can help disguise your Tor traffic so it looks like regular HTTPS traffic, bypassing detection systems that look for Tor's telltale signs.
Summary:
Try a Tor + residential proxy setup.
Rotate your exit nodes if you get blocked.
Ensure there are no DNS or WebRTC leaks.
Consider obfuscating your Tor traffic if needed.
If you keep hitting roadblocks, you might need to experiment with different configurations or explore more advanced setups, but this should help you get a solid start.
You might have some value in a browser based vnc connection which some providers allow and you can install yourself. You will have the same issue that it is slow and probably will disconnect constantly. You are probably blocked because of the provider or because of the exit node.
i think the problem is with the proxies
preconfigured vnc is bad idea because who knows how they configured encryption he will leak everything to tor exit node
vnc should be set up manually from terminal
You are right that by default the preconfigure vnc is not encrypted and would have to be manually encrypted. Web based RDP is an option but is slower than a regular rdp client. I think at the end adding a proxy is not necessary and he can make RDP work with tor but I would be suspicious that it does not leak information or go around the tor routing if not using something like tails or whonix.