I am not sure, but I am guessing you might be encountering a blank page?
This is copy-pasted from my reddit post: https://old.reddit.com/r/TOR/comments/lmrdk6/tor_browser_safest_security_and_duckduckgo/
How to fix it
Enable noscript in the NoScript options:
Click on the hamburger menu (three bars in the top right corner)
The three dots for NoScript
None of the 3 languages is perfectly safe. All of them have vulnerabilities that if an application is not developed following good programming practices, they can allow an attacker to exploit different weak points and gain access to the application and its data.
You can use any language you want, but you have to consider checking your application to see if ...
Take a look at this site: https://tails.boum.org/support/known_issues/
For me the internal keyboard of the Microsoft Surface Laptop 2 doesen't work. I use a bluetooth keyboard with an USB dongle.
For the installation process I followed this guide: https://www.youtube.com/watch?v=QmBfmv6Wn9E&t=136s and also used etcher to flash the .img-file to the USB ...
Tor clients keep a pool of circuits and may use several circuits simultaneously for streams depending on factors such as exit policies, stream isolation, etc. So there is generally not a single "in-use" circuit. And it's not quite true that a circuit is used for only a max of 10 minutes. Generally a circuit is marked as "dirty" (unusable ...
Unfortunately an old issue. Moved and closed several times but still not resolved:
Distribute IPv6 bridges through bridges.torproject.org.
BridgeDB so far only works for IPv6 vanilla bridges.
I have 2 IPv6 obfs4 bridges running in Germany. If you want the IP's mail me (+gpg-key) or use keybase.
Sadly, getting bridges from bridges.torproject.org automatically to torrc is not possible without some kind of automation. As for what can be done, you have these options:
Make a program that solves captchas (you can use "captcha solving services" for that, just google it and you'll find a bunch of sites that can do that) for you and sets the ...
In case you want to build (compile) and install Tor from source code, you can follow these steps:
Install pre-requisites, in this example I used a Debian based GNU Linux distribution:
sudo apt install -y git build-essential automake libevent-dev libssl-dev zlib1g-dev
Clone Tor from git.torproject.org:
git clone https://git.torproject.org/tor....
I would suggest you start with chutney enter link description here and see how chutney works by setting up a what you need which is: directory authorities, relays, exit relays and a client. Start with the networks/basic-min template and from there you can build to the type of network you are looking to design. You do need directory authorities and chutney ...
TL;DR: It’s complicated. It depends on your threat model and how well you configure everything.
This is one of the top questions on the Tor Project site . They recommend VPNs (with Tor) only for advanced users and refer to a wiki entry for details.
The discussion below is a summary of the wiki entry, together with some thoughts of mine:
The arrangement ...
It is possible to set your homepage to a file:// URL so the homepage can be loaded from a text or HTML file on your local computer (rather than a URL on the internet). If it is plain text, the links won't be clickable.
When you open Tor, the new home page is used instead of the default Tor page.
Make a simple HTML file with your bookmarks in it and point the ...
HTTPS Everywhere does not block all non-https requests since it would block a significant fraction of the Internet for users, hurting usability. Instead, it uses a ruleset to only modify requests for specific domains. You can search the list here: https://atlas.eff.org/index.html. Note that uniquemachine.org is not in the list, so the HTTPS Everywhere ...
Is there any specific reason for using command line parameters instead of torrc?
I'd guess that cli parameters have precedence default settings, which it is using:
[notice] Configuration file "C:\Users\Username\AppData\Roaming\tor\torrc" not present, using reasonable defaults.
It's also reporting it's not finding geoip:
Dec 31 22:03:29.215 [warn] ...
The error Failed to open GEOIP file C:\Users\Username\AppData\Roaming\tor\geoip is the important one here. If tor can't open the geoip file, it doesn't have any location data for any relay.
Since the path is relative, you need to run tor.exe from the correct directory. So use the cd command to change directories, probably to C:\Users\Username\workspace\test\...
Currently, there is only two official methods of using Tor on Android:
If you only need the Tor Browser, you can download the release version of it (F-Droid) or the alpha version of it (F-Droid) for Android.
If you need to use tor outside of Tor Browser, you can use Orbot (F-Droid) VPN mode (promiscuous mode for root users have been discontinued a long time ...
Nick Mathewson answered the question here: https://gitlab.torproject.org/tpo/core/tor/-/issues/40386#note_2735298
That sounds plausible to me. I'd suggest adding a step 0: make sure that the path is somewhere randomly generated that only you have write access, to eliminate the risk of somebody else writing to it. (Using mkstemp or similar should take care ...
Ok it seems that pacman was the culprit here, not tor.
I had a torrc.pacnew file which was causing the problem. I managed to fix it by doing the following:
mv /etc/tor/torrc.pacnew /etc/tor/torrc
Then I just added my personal configurations to the file
Depending on the tor version it is either hidden service v2 or v3 which is the default. And I think it is v3 in your case.
in your hidden service definition and retry.
Please also note that hidden service v2 support will be removed from tor network in the near future (this year if I remember correctly) so you should ...
No, even if the user is using dark mode, light mode, or some other theme (system theme or app theme), this cannot be used to fingerprint the user if they are using the Tor browser. Detecting dark mode or light mode does not even work with the Tor browser. This does not affect the user's anonymity, privacy, or security in any way.
Normally you can use CSS, ...
The resolution was pretty simple , due to running tor and openvpn both locally the tor data was also trying to go through openvpn when openvpn was enabled. And openvpn was trying to send all data through tor socks , thus causing this issue. It was simply resolved by adding the following in the openvpn config after the socks option:
route bridgeip ...
After reading a bit, I've come to believe that this particular extension may or may not affect your anonymity. It's complicated and for me, I wouldn't use it. (I believe) it's just not worth the risk given that even one error can completely deanonymize you. Here's what I found:
On KeePassXC-Browser extension's private policy (https://addons.mozilla.org/en-...
I also tried to open the Shutterstock site and got the same error message. Furthermore I used several different exit relays. All resulting in the same message.
So I assume they block the Tor network. Also the message "406 Not Acceptable" indicates it.
You can try to reach out to them and ask why they're blocking the network. Sometimes companies ...
On Mac OS, the torrc is in the Tor Browser Data directory at ~/Library/Application Support/TorBrowser-Data/Tor.
Note the Library folder is hidden on newer versions of macOS. To navigate to this folder in Finder, select "Go to Folder..." in the "Go" menu.
Then type ~/Library/Application Support/ in the window and click Go.
To be clear, this will not make all of your applications anonymous, and you will certainly leak information when applications either don't use the proxy, use it incorrectly, or send identifying information over the proxy. In addition, non-TLS HTTP traffic will be readable by the exit relay. If you're not concerned about anonymity...
Tor only provides a ...
After looking into this again after leaving it for a long time, I quickly found the solution.
It turned out that the files in the /var/lib/tor/keys folder were not owned nor writable for the debian-tor user. Make sure to set debian-tor as the owner and allow this user to read and write the files.
chown -R debian-tor /var/lib/tor/keys/*
chmod 600 /var/lib/tor/...
As per changelog, Tor, starting with 0.4.6, no longer publishes any DirPort:
Removed features (relay):
Because DirPorts are only used on authorities, relays no longer advertise them. Similarly, self-testing for DirPorts has been
disabled, since an unreachable DirPort is no reason for a relay not to
advertise itself. (Configuring a DirPort will still work, ...
As of March 2021, it appears the HARICA, a certificate authority based in Greece, also allows you to obtain an SSL certificate for a .onion domain. While HARICA offers them cheaper,
To quote their website, one of the types of certificates they offer is listed as
SSL DV Onion (Domain Validated - Onion): SSL/TLS Server Certificate that includes one or more ...
As of February 2020, this is now technically possible, but it has yet to be implemented by Let's Encrypt.
Why https for .onion domains?
First, I think it's necessary to point out that there are non-security-related, logistical reasons for why you'd want to add a valid TLS cert for a website served on an onion service: there are many tools/protocols that are ...