no actual changes to the license.

this way folks who don't immediately recognize the text of the 3-clause
bsd can be reassured that we're using a standard license.

closes ticket #31498

We shouldn't actually need this code nearly anywhere we build:
getdelim is POSIX, and mingw provides it.

We need to define this function when compiling with clang -m32 -ftrapv,
since otherwise we get link errors, since apparently some versions
of libclang_rt.builtins don't define a version of it that works? Or
clang doesn't know to look for it?

This definition is taken from the LLVM source at
  https://llvm.org/svn/llvm-project/compiler-rt/trunk/lib/builtins/mulodi4.c

I've also included the license (dual BSD-ish/MIT-ish).

This is taken verbatim from openssh 6.8p1, which appears to have
lightly tweaked it from the openbsd version.

Because in 95 years, we or our successors will surely care about
enforcing the BSD license terms on this code.  Right?

siphash is a hash function designed for producing hard-to-predict
64-bit outputs from short inputs and a 128-bit key.  It's chosen for
security and speed.

See https://131002.net/siphash/ for more information on siphash.

Source: https://github.com/majek/csiphash/

This M4 module lets us learn the right way (out of at least 18
possibilities) to extract the current PC for stack-trace-fixup-in-signal
purposes.  The Google Performance Tools license is 3-clause BSD.

There are as many divergent implementations of sys/queue.h as there
are operating systems shipping it, it would seem.  They have some code
in common, but have drifted apart, and have added other stuff named
differently.  So I'm taking a relatively sane one, and hoping for the
best.

I'm taking OpenBSD's in particular because of the lack of external
dependencies, the presence of a CIRCLEQ (we could use one of those in
places), and the liberal licensing terms.

I'm naming the file tor_queue.h, since historically we've run into
trouble having headers with the same names as system headers (log.h,
for example.)

when tor starts.
this breaks rpms and maybe other packages.


svn:r14764

svn:r13014

svn:r12786

svn:r12035

 At the start of the LICENSE and AUTHORS files, explain "LICENSE for what? AUTHORS of what?"  Apparently this has confused some people, who see our names in an AUTHORS file in a bundle, and so decide that we must be the go-to people tor tech support on the bundle.


svn:r10524

 Update copyright dates.


svn:r9570

svn:r5716

svn:r5629

if some of our packages statically link any openssl libs.


svn:r5334

svn:r4798

and strlcpy/strlcat.c so when we do a binary distribution (e.g. win32
installer, rpm, or os x package) we're not violating their licenses.


svn:r3269

svn:r2763

svn:r1291

svn:r907

svn:r561

svn:r560