removing deploy from travis-ci
Grandstream ATA decoder
SetDateSave off in ossec-installer.nsi

Turned SetDateSave to off. Reference http://nsis.sourceforge.net/Reference/SetDateSave for more information on what this does. While keeping the original DateModified times has some advantages I think not having NSIS overwrite the new DateModified times with the originals is much better. It lets the user see when a file was actually modified.
Merge pull request #123 from mstarks01/master

Grandstream ATA decoder
Fixes to ossec-installer.nsi

Explicitly set SetOverwrite to on. This is the default but for clarity it is good to show exactly what action we are hoping to take with these files.
Use file command in ossec-installer.nsi

Use the full ability of the the File command. Before when upgrading and doing a Rename after without the /Reboot command most of those commands would "fail silently" which is the best way I can describe it. It would just leave these files in the main ossec-agent directory never really upgrading parts of the system. Using the File command has the added benefit of complaining if a file is in use during the installation. For example have the win32ui.exe open and try to run a new installation. It hould complain that the file is inaccessible until the application is closed. Previously, this would just leave os_win32.exe in the ossec-agent directory and never successfully upgrade the executable.
Update manage_keys.c

Log the cacls command about to be run.
Added /? as a parameter to ossec-agent on win32

Added /? as a help parameter. This is a pretty standard way of getting help information from other command line executable's on Windows.
Merge pull request #128 from awiddersheim/patch-9

Added /? as a parameter to ossec-agent on win32
Fixes to win32 services

There were quite a few issues with the win32 service code that this
corrects. The first is that some of the comments in the code needed
to be updated. Looks like code was copied and reused but the comments
were not updated to reflect what the reused code was doing.

There was the potential in InstallService() where not all the service
handles would be closed if errors were hit at certain spots.

Before installing a new service the old service was not uninstalled.
This is desireable in the case where the new service has different
options or points to a different path location for example. In some
cases it might be bad where some type of user change was made but that
is difficult to account for. I leaned toward cleaning up the old so that
the new service can be installed fresh.

This also causes an error when the service goes to install because the service
already exists. This would actaully happen each time the OSSEC installer was ran
but due to some incorrect logging statements (which I'll explain below) a blank
line would appear.

When doing an uninstall of a service the service wasn't stopped prior to
the uninstallation. This would leave the service running until the service
was stopped or the computer rebooted at which point the service would dissappear.
It is better to stop the service before unintsalling. I'd imagine that is what
the user would expect to happen during such an operation.

The logging in this code was not done correctly. Namely, the call to merror()
in the InstallService() function after the "install_error" label was completely
wrong and would result in a nearly blank line in the logs. There were also reports
of times where a user would install the agent on a win32 machine and everything
would work except the service would never register. Fixing all of the logging to
use verbose() should hopeflly lead to better troubleshooting of errors like that
in the future.
Show details during win32 installation

When doing a win32 installation the details are hidden and only shown
very briefly. In some cases when doing an Exec on some of the OSSEC
command line tools it will spawn a cmd.exe that only appears for a
second. Some of the details those processes do are logged in the
ossec.log but it would be nice if they were also displayed in the details
window and those details can be reviewed.

Changed all Exec's to use ExecToLog so their details show up in the
installer details section.

Configured the details to be displayed by default and to not skip
past the details page automatically when the installation is completed.

This also has the added benefit of now popping up cmd.exe windows when
an installation takes place.
Added error checking to ossec.conf installation
Merge pull request #127 from awiddersheim/patch-8

Update manage_keys.c
Merge pull request #130 from awiddersheim/fix_win32_installer_details

Show details during win32 installation
Merge pull request #126 from awiddersheim/patch-7

Use file command in ossec-installer.nsi
merging in
mergin
Merge pull request #129 from awiddersheim/fix_win32_service

Fixes to win32 services
Merge pull request #131 from awiddersheim/fix_win32_installer_conf_error_checking

Added error checking to ossec.conf installation
Merge pull request #121 from jrossi/remove-deploy-travis-ci

removing deploy from travis-ci