Illustration by Alex Castro / The Verge
If you’re concerned about privacy and want one of the most well-protected browsers available — and don’t mind that it may prevent you from using certain websites — then you should try the Tor Browser.
The name Tor stands for The Onion Routing, which was the original description of how the open-source browser anonymizes its users. As Tor’s site explains, it does this by encrypting your information and relaying it through Tor’s system of servers (called a circuit), so that your ISP can’t track your activity. Different tabs originating from the same website will all be loaded through the same circuit.
As a result, according to Tor, websites and browsers will identify your connection as coming from the Tor network. While this efficiently protects your identity, it can also become troublesome with sites such as financial institutions or medical services that see your login as not coming from your home computer. It can also slow things down.
(A note: you may have read a lot about Tor and the dark web. Don’t sweat it. The Tor Browser just bundles Tor tech into a Firefox wrapper, so using this browser doesn’t mean you’re suddenly going to stumble onto the dark web.)

Adjust your tracking settings

To see what servers your data is being bounced through, you can click on the green lock icon on the left side of the address bar. If you’re having trouble getting the site to load properly you can try to adjust it by clicking on the “New Circuit for this Site” button, which will reroute the data and possibly solve the problem.
As mentioned above, the Tor Browser is based on Firefox, which is why some of the interface and controls may look familiar if you’re a Firefox user.
When you install the Tor Browser, it is set by default to private browsing mode, which will delete all cookies and site data when the browser is closed. (It will also delete them when you restart it using the “New Identity” function, which is the broomstick icon to the right of the address bar.) You can disable private browsing mode if you want to keep some of your cookies or data. Here’s how:
  • Click on the three bars in the top right corner of the browser window. Go to “Options” (on a PC) or “Preferences” (on a Mac).
  • Go to “Privacy & Security” on the left-hand menu.
  • Find the “History” section in the main area and uncheck “Always use private browsing mode.” You will need to restart the browser; you can then choose what you want it to remember when you exit (such as your brows
  • ing and download history).
you want to manually delete cookies or other data during a browsing session:
  • In the “Privacy & Security” section, look for “Browser Privacy” (which will be the first section on the page. Find “Cookies and Site Data” and click on “Manage Data…”
  • You can then use the “Remove Selected” button to remove data from a particular site or just click “Remove All” to delete all of it.
  • On the “Browser Privacy” page, you can also click on “Manage Permissions…” to specify what cookies should be blocked or allowed for individual websites. Enter in the URL and then select either “Block,” “Allow for Session,” or “Allow.”
  • Finally, you can select “Clear Data” to delete all cookies and data currently stored by the browser.

Fingerprinting and ad-blocking

According to the browser’s support page, Tor offers strong protection against fingerprinting. “Tor Browser is specifically engineered to have a nearly identical (we’re not perfect!) fingerprint across its users,” it says. “This means each Tor Browser user looks like every other Tor Browser user, making it difficult to track any individual user.”
The Tor Browser doesn’t block ads, but Tor also recommends that you don’t install extensions as they may cause privacy or functionality issues. As a result, while Tor protects you against tracking, you may still have to put up with the presence of the ads themselves.
Vox Media has affiliate partnerships. These do not influence editorial content, though Vox Media may earn commissions for products purchased via affiliate links. For more information, see our ethics policy.

How to use Restricted Shell to limit user access to a Linux system

Learn how to prevent Linux users from executing certain commands and confining them to their home directory by employing rbash.



How to use Restricted Shell to limit user access to a Linux system
You have users logging in to your Linux system. Those users might have not have sudo rights, but they quite possibly could have free rein to poke around most of the system directory tree. You don't want that. Why? Although those users might not be able to edit the vast majority of your configuration files, you certainly don't want those users viewing them. Same holds true for your client data--you want that locked down.
But how do you prevent users from being able to access your directory hierarchy without having to tweak the permissions of every file and folder on the system, which could seriously complicate things? 
One way is by employing a tool called Restricted Bash (rbash). With rbash you can prevent a user from:
  • Using the cd command
  • Modifying the values of $PATH, $SHELL, $BASH_ENV, or $ENV
  • Executing programs that contain a /
  • Redirecting output using >, >|, <>, >&, &>, and >>
  • Get out of restricted mode within scripts
  • Turn off restricted mode

What you'll need

  • A running instance of Linux
  • A user with sudo privileges

How to create a test user

We're going to create a test user on a system. We'll call that user vega. We want to create the user such that their shell is rbash. This is done with the command:
sudo useradd -m vega -s /bin/rbash
You'll then need to give the new user a password with the command:
sudo passwd vega
When prompted, type and verify a password for the new user.

How to create a directory

Now we're going to create a directory for the new user that will house the only commands the user is allowed to run. Say, for instance, we want to allow the user to issue the commands mkdir, ls, and ssh. First let's create the directory with the command:
sudo mkdir /home/vega/bin
Next, we're going to create links into that newly created directory for the commands the user can run (again mkdir, ls, and ssh). To do this, issue the commands:
sudo ln -s /bin/mkdir /home/vega/bin
sudo ln -s /bin/ls /home/vega/bin
sudo ln -s /bin/ssh /home/vega/bin

How to prevent profile modification

Now we need to make sure the new user is unable to modify their .profile file. Before we can actually change the permissions and ownership of the .profile, you'll need to log in as that user, so the file is created. After you've logged in, log back out and back in as a user with sudo privileges.
Change the ownership and permissions of the file with the commands:
sudo chown root. /home/vega/.profile
sudo chmod 755 /home/vega/.profile

Testing

Log in to the server with the vega account and issue the command:
cd /
You should be informed that you are restricted from using the cd command (Figure A).
Figure A

rbash-error.jpg
No dice with the cd command.

You can try any command you like, but only mkdir, ls, and ssh will work for the vega user.
And that's how you can heavily restrict users on a Linux system with rbash. This is a really handy way to control what commands your users can execute and how they can move about within the directory structure.

Also see