New answers tagged

0

just 3 steps: Run a VM/box dedicated to Tor Route all the rest of the traffic through it - except the Tor node one Do not confirm your phone, e.t.c... = keep a digital hygiene up And it will work for sure


0

Yes so far you are correct. If your only threat model is your university, you may use VPN/ssh tunneling whatever, which may be faster than tor and wont use so much resources for such a simple task. If your threat model includes more than that, you might need tor.


0

Well, it looks like they're using a Cloudflare or a similar service to do tor blocking and CDN service. They do track you as you're using their service, so - discard them, there's nothing more you can do from your side


0

Unless your university is exceptionally vigilant, using an obfs4 bridge will make your traffic look like nothing, from their point of view.


0

This seems like the letterboxing feature witch is used to avoid fingerprinting. Try turning privacy.resistFingerprinting.letterboxing to false to get rid of it. That is all I know about the letterboxing feature. Hope this helps.


0

It does load just fine from EU. They will just block tor traffic, because, like, who activates his cc via tor won't do good, they think.


0

Well, you don't need anything except the NGinx and tor running on the same box: in nginx server block you utilize the include ability - so you will have two server blocks for defining listening address - a clearnet IP for open web and 127.0.0.7 for Tor - and separate logging, separate HTTPS certificates with corresponding host names in them to avoid ...


0

Tailscale is not the right choice to do it out of the box and you need it vice versa: you need to use OpenVPN from your NAT'ed box to the VPS and the client here should be a NAT'ed box. After that just forward the port VPS->NATed via static OpenVPN internal IP's and make the NAT for tor process user through the VPN tunnel. Then self-check will succeed and ...


0

Check your tb logs - the Tor Browser Bundle has it's own tor supplied with it and until it's 100% bootstrapped - neither a side app(burpsuite in your case) nor the tb itself will not work. The Tb's Tor log has a full answer for your problem, it's nowhere else to look


0

Try setting the Address option in your torrc file to the public address of your VPS. From the tor man page: Address address The IPv4 address of this server, or a fully qualified domain name of this server that resolves to an IPv4 address. You can leave this unset, and Tor will try to guess your IPv4 address. This IPv4 address is the one used to ...


1

Please note that Tor Browser comes bundled with it's own tor which is separate from the little-t-tor you're running on the command-line. To use bridges with little-t-tor you will have to manually edit your torrc (located at /etc/tor/torrc) and add the following lines: UseBridges 1 Bridge <bridge address> Also see: https://support.torproject.org/...


-1

https://github.com/alecmuffett/eotk This is a way to do it. There is also a way to do it with OnionShare. https://onionshare.org/


0

I realize that the question was asked about a year ago, but I will respond hoping that it would be useful for someone given the ongoing v2 onion services deprecation. Assuming you already created a version 3 address i.e in torrc add these lines: HiddenServiceDir /full/path/to/your/new/v3/directory/ HiddenServicePort <virtual port> <target-address>...


0

Are you still running into this issue with the latest version of Tor Browser (10.5.5)? If yes, it would be immensely helpful if you can find any lines beginning with [WARN] in your Tor logs.


0

I found article on website about tor proxy https://itgala.xyz/nginx-reverse-proxy-to-onion-site-in-tor-network/ I wanted to mirror any tor website to my tor site My Nginx config: /etc/nginx/sites-enabled/hy-reverse server { listen 127.0.0.1:80 default_server; server_name localhost; root /var/www/site1; index index.html index....


Top 50 recent answers are included