Anonymous Browsing - Revision history

Unknown user: /* Traffic Location Anonymization */

2020-07-05T18:17:01Z

Traffic Location Anonymization

← Older revision		Revision as of 18:17, 5 July 2020
Line 156:		Line 156:
	Traffic location anonymization is what Tor gets you. Tor anonymizes the location of origin of your traffic, by passing it through three layers of obfuscation: the Tor entry node, the Tor bridge node, and the Tor exit node. Each connection, between each layer, is made randomly, and each connection obfuscates further the geographic origin of the traffic. While this slows down traffic significantly, it also bounces your traffic all over the place, rendering it untraceable.		Traffic location anonymization is what Tor gets you. Tor anonymizes the location of origin of your traffic, by passing it through three layers of obfuscation: the Tor entry node, the Tor bridge node, and the Tor exit node. Each connection, between each layer, is made randomly, and each connection obfuscates further the geographic origin of the traffic. While this slows down traffic significantly, it also bounces your traffic all over the place, rendering it untraceable.

	(Assuming~~, of course,~~ you ~~aren~~'t ~~sending~~ your ~~name and address~~ over Tor ~~unencrypted. See above~~.)		(Assuming you don't do something stupid like log in to your Facebook account over Tor.)



	{{AnonymousBrowsingFlag}}		{{AnonymousBrowsingFlag}}

Unknown user: /* Option 3: Anonymous SSH + Socks */

2020-07-05T18:14:41Z

Option 3: Anonymous SSH + Socks

← Older revision		Revision as of 18:14, 5 July 2020
Line 129:		Line 129:

	[[Anonymous SSH]] - covers how to create an anonymous SSH connection to a remote machine over Tor.		[[Anonymous SSH]] - covers how to create an anonymous SSH connection to a remote machine over Tor.

			[[Anonymous SSH and Socks]] - covers how to use SOCKS to send web traffic over an anonymous SSH connection to a remote machine over Tor

	===Option 4: Anonymous Stunnel===		===Option 4: Anonymous Stunnel===

Unknown user: /* Option 3: Anonymous SSH + Socks */

2020-07-05T18:14:15Z

Option 3: Anonymous SSH + Socks

← Older revision		Revision as of 18:14, 5 July 2020
Line 124:		Line 124:
	===Option 3: Anonymous SSH + Socks===		===Option 3: Anonymous SSH + Socks===

	One method ~~would be to connect to~~ a remote machine ~~via~~ an [[SSH]] tunnel~~, routing~~ the traffic for that tunnel ~~starting with~~ the ~~encryption, at your computer,~~ before it ~~leaves to~~ the network; ~~through~~ port 9050 ~~and out~~ to the Tor entry node; through the Tor bridge node~~; out again on the other side via~~ the Tor exit node~~; and finally~~, to the ~~computer you're connecting to~~. This ~~configuration would allow a regular~~ SSH ~~connection, or it~~ could be ~~an SSH tunnel for carrying~~ browser traffic and web requests ~~(i.e.,~~ requests made locally are forwarded to ~~the~~ remote machine ~~via the~~ SSH tunnel). ~~Alternatively, the tunnel could carry an X session, with~~ the ~~user running a (local) browser window corresponding to~~ a ~~browser instance on the remote machine~~.		One method that utilizes a remote machine (one on a safer network or with less aggressive surveillance) involves an [[SSH]] tunnel to the remote machine. The traffic for that tunnel is encrypted on the local machine before it is ever on the network; it stays encrypted as it is passed to Tor, which sends it out on port 9050 to the Tor entry node, through the Tor bridge node, and through the Tor exit node, until it comes out the other side at the "safe" remote machine.

			This SSH tunnel could be utilized to carry browser traffic and web requests - requests made locally are forwarded to a remote machine through SSH tunnel. This requires the use of a SOCKS proxy.

	[[Anonymous SSH]] - covers how to create an anonymous SSH connection to a remote machine over Tor.		[[Anonymous SSH]] - covers how to create an anonymous SSH connection to a remote machine over Tor.

Unknown user: /* Option 3: Anonymous SSH + Socks */

2020-07-05T18:10:57Z

Option 3: Anonymous SSH + Socks

← Older revision		Revision as of 18:10, 5 July 2020
Line 124:		Line 124:
	===Option 3: Anonymous SSH + Socks===		===Option 3: Anonymous SSH + Socks===

	One method would be to connect to ~~the~~ machine via an [[SSH]] tunnel, routing the traffic for that tunnel starting with the encryption, at your computer, before it leaves to the network; through port 9050 and out to the Tor entry node; through the Tor bridge node; out again on the other side via the Tor exit node; and finally, to the computer you're connecting to. This configuration would allow a regular SSH connection, or it could be an SSH tunnel for carrying browser traffic and web requests (i.e., requests made locally are forwarded to the remote machine via the SSH tunnel). Alternatively, the tunnel could carry an X session, with the user running a (local) browser window corresponding to a browser instance on the remote machine.		One method would be to connect to a remote machine via an [[SSH]] tunnel, routing the traffic for that tunnel starting with the encryption, at your computer, before it leaves to the network; through port 9050 and out to the Tor entry node; through the Tor bridge node; out again on the other side via the Tor exit node; and finally, to the computer you're connecting to. This configuration would allow a regular SSH connection, or it could be an SSH tunnel for carrying browser traffic and web requests (i.e., requests made locally are forwarded to the remote machine via the SSH tunnel). Alternatively, the tunnel could carry an X session, with the user running a (local) browser window corresponding to a browser instance on the remote machine.

	[[Anonymous SSH]] - covers how to create an anonymous SSH connection to a remote machine over Tor.		[[Anonymous SSH]] - covers how to create an anonymous SSH connection to a remote machine over Tor.

Admin at 03:44, 25 September 2015

2015-09-25T03:44:14Z

@@ Line 19: / Line 19: @@
 [[Proxychains]] - a program allowing you to run other programs through a proxy. This means you could, for example, run [[Nmap]] through a proxy server, or run it through Tor.
 =How The Tools Fit Together=
@@ Line 33: / Line 49: @@
 * Content Filter
 * Traffic Encryption
 * Traffic Location Anonymization
@@ Line 40: / Line 57: @@
 The browser (I'll presume Firefox) is the final recipient of HTTP (port 80) and HTTPS (port 443) traffic. It renders what it receives into web pages. By itself, Firefox doesn't do a whole lot to protect you. It might warn you of bad certificates, but it won't block Javascript (although you can use the NoScript Extension) or cookies (although you can change the preferences) or strip out malicious headers (you gotta use Greasemonkey Extension for that).
 * Install NoScript Extension

Admin: /* The Traffic Firewall */

2015-08-29T19:29:55Z

The Traffic Firewall

← Older revision		Revision as of 19:29, 29 August 2015
Line 59:		Line 59:
	You'll be surprised, if you use the NoScript Extension, how pervasive cross-domain embedded Javascript is, and how many websites the scripts on a given page are communicating with.		You'll be surprised, if you use the NoScript Extension, how pervasive cross-domain embedded Javascript is, and how many websites the scripts on a given page are communicating with.

	==~~The~~ Traffic Firewall==		==Traffic Firewall==

	A traffic firewall is a wall between you and the outside world. It prevents unwanted traffic from getting in, and it prevents unwanted traffic from getting out.		A traffic firewall is a wall between you and the outside world. It prevents unwanted traffic from getting in, and it prevents unwanted traffic from getting out.

	For example, a firewall could be used to block port 22, so that even if you have an SSH server running on your computer for local network connections, no remote connections from outside could be made to port 22.		For example, a firewall could be used to block port 22, so that even if you have an SSH server running on your computer for local network connections, no remote connections from outside could be made to port 22.

			However, this can also prevent unwanted traffic from going out - for example, by blocking port 53, which is the port normally used for DNS queries, you prevent some idiotic program that has implemented its own DNS query engine from broadcasting your native MAC and IP address.

	Firewall rules:		Firewall rules:
	* Block all ports except port 9050		* Block all ports except port 9050
	* Block all DNS resolving queries sent from your client to any DNS server~~, and block~~ DNS queries made by clients toward external IP addresses on UDP port 53~~, forcing all~~ DNS queries ~~to go~~ through Tor.		* Block all DNS resolving queries sent from your client to any DNS server
			* Block DNS queries made by clients toward external IP addresses on UDP port 53
			* Force DNS queries through Tor (port 9050)

	==Traffic Encryption==		==Traffic Encryption==

Admin: /* The Traffic Firewall */

2015-08-29T19:26:00Z

The Traffic Firewall

← Older revision		Revision as of 19:26, 29 August 2015
Line 60:		Line 60:

	==The Traffic Firewall==		==The Traffic Firewall==

			A traffic firewall is a wall between you and the outside world. It prevents unwanted traffic from getting in, and it prevents unwanted traffic from getting out.

			For example, a firewall could be used to block port 22, so that even if you have an SSH server running on your computer for local network connections, no remote connections from outside could be made to port 22.

	Firewall rules:		Firewall rules:

Admin: /* The Content Filter */

2015-08-29T19:24:10Z

The Content Filter

← Older revision		Revision as of 19:24, 29 August 2015
Line 58:		Line 58:

	You'll be surprised, if you use the NoScript Extension, how pervasive cross-domain embedded Javascript is, and how many websites the scripts on a given page are communicating with.		You'll be surprised, if you use the NoScript Extension, how pervasive cross-domain embedded Javascript is, and how many websites the scripts on a given page are communicating with.

			==The Traffic Firewall==

			Firewall rules:
			* Block all ports except port 9050
			* Block all DNS resolving queries sent from your client to any DNS server, and block DNS queries made by clients toward external IP addresses on UDP port 53, forcing all DNS queries to go through Tor.

	==Traffic Encryption==		==Traffic Encryption==

Admin: /* Option 3: Anonymous SSH */

2015-08-29T19:20:20Z

Option 3: Anonymous SSH

← Older revision		Revision as of 19:20, 29 August 2015
Line 87:		Line 87:
	Another option is to use a private proxy service (paid for with bitcoin, of course) to maintain encrypted connections over Tor. You can maintain an encrypted connection to the proxy server, which then makes all of your requests for you. While this doesn't do anything to protect the web requests made from that proxy server, it is a way of protecting your identity when making requests to that proxy server.		Another option is to use a private proxy service (paid for with bitcoin, of course) to maintain encrypted connections over Tor. You can maintain an encrypted connection to the proxy server, which then makes all of your requests for you. While this doesn't do anything to protect the web requests made from that proxy server, it is a way of protecting your identity when making requests to that proxy server.

	===Option 3: Anonymous SSH===		===Option 3: Anonymous SSH + Socks===

	One method would be to connect to the machine via an [[SSH]] tunnel, routing the traffic for that tunnel starting with the encryption, at your computer, before it leaves to the network; through port 9050 and out to the Tor entry node; through the Tor bridge node; out again on the other side via the Tor exit node; and finally, to the computer you're connecting to. This configuration would allow a regular SSH connection, or it could be an SSH tunnel for carrying browser traffic and web requests (i.e., requests made locally are forwarded to the remote machine via the SSH tunnel). Alternatively, the tunnel could carry an X session, with the user running a (local) browser window corresponding to a browser instance on the remote machine.		One method would be to connect to the machine via an [[SSH]] tunnel, routing the traffic for that tunnel starting with the encryption, at your computer, before it leaves to the network; through port 9050 and out to the Tor entry node; through the Tor bridge node; out again on the other side via the Tor exit node; and finally, to the computer you're connecting to. This configuration would allow a regular SSH connection, or it could be an SSH tunnel for carrying browser traffic and web requests (i.e., requests made locally are forwarded to the remote machine via the SSH tunnel). Alternatively, the tunnel could carry an X session, with the user running a (local) browser window corresponding to a browser instance on the remote machine.

Admin: /* Not An Option: Anonymous Squid */

2015-08-28T17:52:24Z

Not An Option: Anonymous Squid

← Older revision		Revision as of 17:52, 28 August 2015
Line 99:		Line 99:
	[[Anonymous Stunnel]] - covers how to create an anonymous SSL tunnel on port 443 to carry arbitrary traffic (SSH tunnels, etc) over Tor.		[[Anonymous Stunnel]] - covers how to create an anonymous SSL tunnel on port 443 to carry arbitrary traffic (SSH tunnels, etc) over Tor.

	===~~Not~~ An Option: Anonymous Squid===		===Maybe An Option: Anonymous Squid===

	Another (theoretically) good alternative is to forward HTTPS traffic from your computer to the remote computer by running a proxy server on the remote computer - something like [[Squid]]. With Squid, you could make a secure HTTPS connection to the remote machine, protecting your connection on potentially hostile networks (like Tor).An HTTPS connection to the remote machine would be unsniffable by Tor exit nodes, and would then be translated into a web request on the remote end, which the remote proxy server would perform.Encryption happens on the local machine, before it enters Tor, and at the remote machine, before the traffic is returned via Tor. This means a Tor exit node has no way to sniff the unencrypted traffic.		Another (theoretically) good alternative is to forward HTTPS traffic from your computer to the remote computer by running a proxy server on the remote computer - something like [[Squid]]. With Squid, you could make a secure HTTPS connection to the remote machine, protecting your connection on potentially hostile networks (like Tor).An HTTPS connection to the remote machine would be unsniffable by Tor exit nodes, and would then be translated into a web request on the remote end, which the remote proxy server would perform.Encryption happens on the local machine, before it enters Tor, and at the remote machine, before the traffic is returned via Tor. This means a Tor exit node has no way to sniff the unencrypted traffic.
Line 107:		Line 107:
	So the Stunnel and SSH methods above will have to suffice.		So the Stunnel and SSH methods above will have to suffice.

	====Summary====		===Summary===

	Think of it like this: you want to add extra hops to either end of your encryption "traceroute", so that it is longer than your Tor "traceroute".		Think of it like this: you want to add extra hops to either end of your encryption "traceroute", so that it is longer than your Tor "traceroute".