This seems to fix a crash I was seeing.
Trying to reproduce for the logs.
Merge branch 'ossecalert_decoder_crash'
Lines sent to SMTP server need to be terminated with \r\n, not \n.

Lines sent to SMTP server need \r\n, not just \n
Add a VERY basic deoccder for apparmor, and a couple of rules to
basically ignore things.
The IDs for the rules are in the user range, but that can change later.
Sample log message is from RealRancor on github #234. Hopefully he
can help expand the rules.
Update copyright date
Update the decoder to add the operation. This seems important for
determining how malicious some action is.
Add arule to alert on DENIED messages.

The examples provided by @RealRancor illustrate an issue. The
original examples that were provided were in a syslog format
with "kernel" as the program_name. This made them identify as
iptables log messages. The DENIED examples did not have the syslog
header, and identified as auditd log messages. This work should
probably duplicate what was already done for auditd.
Add a couple of rules for breaking down the operations in the
DENIED log samples. I don't know how much value something like this
really has, but I don't have a lot of experience with apparmor.

On another note, but British may be right. Armour feels more right
than armor.
[os_crypto] update makefiles
[os_crypto] add const qualifiers and use explicit os_md5 and os_sha1 instead of char *
[os_crypto] fix CID 28438
[os_crypto] fix sign compare
[os_crypto] fix CID 28439
[os_crypto] make ErrorExit() as noreturn, for static analysers
[os_crypto] add nonnull attributes where suiteable
[os_crypto] fix sign warnings
[os_crypto] uncomment unnecessary variable cleaning (is cleaned later on)
[os_crypto] reduce variable scope and indent branched code
[os_crypto] use snprintf instead of 3 other string operations
[os_crypto] avoid make -C due to bsd compatibility
[os_crypto] make some casts explicit