This addresses the first part of bug 918. Users are now warned when
they try to use hibernation in combination with a port below 1024
when they're not on Windows. We don't want to die here, because
people might run Tor as root, use a capabilities system or some
other platform that will allow them to re-attach low ports.

Wording suggested by Marian

Manually resolved conflicts on version number; all else applied cleanly.

(Don't crash immediately if we have leftover chunks to free after
freeing chunks in a buffer freelist; instead log a debugging message
that might help.)

(Proposals assigned to others are purely in the realm of speculation.)

We don't need to explain the difference between 2nd preimage and
collision: anybody who doesn't know can use wikipedia.

This way we do not need to rebuild util.c and/or config.c whenever
any unrelated source file in src/common or src/or has changed.

Tor doesn't use SVN anymore, making $Revision$, $Id$ and $Date$
meaningless. Remove them without replacement.

Update the proposal creation instructions to remove the Version
and Last-Modified fields.

More thought is needed on each collision opportunity to figure out how
exploitable it is.

Jacob Appelbaum authored 15 years ago and Nick Mathewson committed 15 years ago

Update Torify to use torsocks by default and to warn when the user is
using the older tsocks program. Update torify and the torify man page
to refelect changes to torify. Add warnings in both.

Nick Mathewson authored 16 years ago and Nick Mathewson committed 15 years ago

Now, when you call tor --digests, it dumps the SHA1 digest of each
source file that Tor was built with.  We support both 'sha1sum' and
'openssl sha1'.  If the user is building from a tarball and they
haven't edited anything, they don't need any program that calculates
SHA1.  If they _have_ modified a file but they don't have a program to
calculate SHA1, we try to build so we do not output digests.

svn:r19377

svn:r19369

svn:r19367

svn:r19356