Sending them on is futile, since we will be told "127.0.0.1" and then
think we've been lied to.  Partial fix for 2822.

Partial fix for ticket 2822.

We never use it, so having it around is pointless.

Suggested by Sebastian

This should be really fast on Intel chips.

It allows us more flexibility on the backend if the user needs to
specify the key and IV at setup time.

We never use it, and it would be a stupid thing if we started using it.

Also reinstate the part of the torify script that checks for torsocks
being installed, so that we can give a more useful message in case it
isn't.

Fixes bug3530 and bug 5180. Patch by ugh.

This was causing crashes during unit test runs, as stack smashing
protections got triggered. Issue spotted by weasel

Conflicts:
	src/or/control.c

This is an "-s ours" commit to avoid taking a5704b1c,
which was a cherry-picked backport of fdbb9cdf to add
a SHA256-HMAC function.

Conflicts:
	changes/bug5090

bug5090 was already merged and corrected in the master branch's changelog.

resolves bug 5402.

Christian Kujau authored 13 years ago and Sebastian Hahn committed 13 years ago

The links we have currently redirect to those new files now.

Discovered by Kevin Bauer. Fixes bug 5373; bugfix on 0.2.3.9-alpha,
where task 4552 added support for two layers of torrc files.

Conflicts:
	src/or/circuitbuild.c

If you set ExitNodes so that only 1 exit node is accepted, the
previous patch would have made you unable to build circuits.

Conflicts:
	src/or/routerlist.c