Tor and vm's Post: 302935944

Sponsored Content

Special Forums Cybersecurity Tor and vm's Post 302935944 by Corona688 on Friday 20th of February 2015 12:00:52 PM

02-20-2015

Registered User

Quote:

Originally Posted by senhortempora

But even this vision making sense. See big companies with a lot of customers, and that now, we all know have corroborated with snooping...

Let me adjust that a little bit. vmware doesn't have billions of individual customers, it has fewer numbers of larger, corporate customers.

It seems okay -- or at least inevitable -- for a company to mess with people's personal information individually these days, but mining someone else's corporation for people's personal information can be seriously big trouble. That's theft, that's information a corporation expects to be paid for.

Corona688

View Public Profile for Corona688

Visit Corona688's homepage!

Find all posts by Corona688

3 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

TOR environment variable

My profile sets the TOR variable to $(whence vi). What is TOR used for? I appreciate any help I can get.

2. Cybersecurity

Problem with Privoxy and Tor

Greetings, I use Debian Wheezy as an OS and I have already downloaded the Tor Browser-Bundle, which works fine. As soon as a start privoxy and set the proxy to: 127.0.0.1:8118 (socks4) in the tor browser (edit-->pref-->advanced-->settings--->http-proxy) I always get a connection refused. I...

3. Forum Support Area for Unregistered Users & Account Problems

Account Register With Tor

Hello, I would be interested in creating an account on this forum. However I have run into trouble in the process, I seem to not have permission to access the registration page. It seems that this forum has blocked registration from Tor. I am wondering if there is any way I could obtain an account...

LEARN ABOUT DEBIAN

arm

arm(1)							      General Commands Manual							    arm(1)

NAME

       arm - Terminal Tor status monitor

SYNOPSIS

       arm [OPTION]

DESCRIPTION

       The  anonymizing  relay	monitor (arm) is a terminal status monitor for Tor relays, intended for command-line aficionados, ssh connections,
       and anyone stuck with a tty terminal. This works much like top does for system usage, providing real time statistics for:
	 * bandwidth, cpu, and memory usage
	 * relay's current configuration
	 * logged events
	 * connection details (ip, hostname, fingerprint, and consensus data)
	 * etc

       Defaults and interface properties are configurable via a user provided configuration file (for an example see the  provided  armrc.sample).
       Releases and information are available at http://www.atagar.com/arm.

OPTIONS

       -i, --interface [ADDRESS:]PORT
	      tor control port arm should attach to (default is 127.0.0.1:9051)

       -c, --config CONFIG_PATH
	      user provided configuration file (default is ~/.arm/armrc)

       -d, --debug
	      writes all arm logs to ~/.arm/log

       -b, --blind
	      disable connection lookups (netstat, lsof, and ss), dropping the parts of the interface that rely on this information

       -e, --event EVENT_FLAGS
	      flags for tor, arm, and torctl events to be logged (default is N3)

		d DEBUG      a ADDRMAP		 k DESCCHANGED	 s STREAM
		i INFO	     f AUTHDIR_NEWDESCS  g GUARD	 r STREAM_BW
		n NOTICE     h BUILDTIMEOUT_SET  l NEWCONSENSUS  t STATUS_CLIENT
		w WARN	     b BW		 m NEWDESC	 u STATUS_GENERAL
		e ERR	     c CIRC		 p NS		 v STATUS_SERVER
			     j CLIENTS_SEEN	 q ORCONN
		  DINWE tor runlevel+		 A All Events
		  12345 arm runlevel+		 X No Events
		  67890 torctl runlevel+	 U Unknown Events

       -v, --version
	      provides version information

       -h, --help
	      provides usage information

FILES

       ~/.arm/armrc
	      Your personal arm configuration file

       /usr/share/doc/arm/armrc.sample
	      Sample armrc configuration file that documents all options

AUTHOR

       Written by Damian Johnson (atagar@torproject.org)

								  27 August 2010							    arm(1)