If we received an event without a content-type header we were
dereferencing a null pointer leading to a seg fault.
Reported-by: Ico <ico@voip-io.org>

ESL-90 --resolve

We were actually checking this indirectly in the loop that follows,
but it's more clear to check this immediately and directly.

- fixed AEAD IV calculation for big-endian machines

This commit resolves issue #46.  The GCM mode was using the wrong master SALT length.  The master SALT should be 96 bits instead of 112 bits.  Note, GCM mode uses the legacy CTR mode for the KDF.  The legagacy CTR mode cipher implementations assume a 112 bit SALT.  Changes to the cipher abstraction layer API are required to provide the ability to specify the SALT length.  For now this commit modifies the SRTP layer to ensure the SALT is zero-appended before initializing the KDF.  This commit also provides public definitions for the GCM cipher suite master key sizes to avoid confusion for application developers.

ESL-89: --resolve add rubymod-install and add ability to use a ruby not in your path by setting RUBY env var

The relevant v8 build issues are believed to be worked out at this
point.

FS-5832  regression.... After this change the sticky completes were deleting.  This should correct it

We can't use their new mb_gets() because they call exit(3) in the
event of a read error, which isn't what we want.

ref: http://my-basic.googlecode.com/svn/trunk@57

...after dos2unix conversion.

Having an unaltered base point in tree makes future merges with
upstream much easier.

ref: http://my-basic.googlecode.com/svn/trunk@54

gets(3) is going away; it's been removed by C11, and gcc now warns on
it, breaking the build.

fix mod_basic clang build warning, we don't need to declare var we don't use on this side of the ifdef