forward port the initial Security work and get it compiling

git-svn-id: http://open-zwave.googlecode.com/svn/branches/2014-03-05-newsecurity@795 db0adee0-878e-11de-bed6-6d316fbe0868
don't know why this was deleted

git-svn-id: http://open-zwave.googlecode.com/svn/branches/2014-03-05-newsecurity@796 db0adee0-878e-11de-bed6-6d316fbe0868
more work on integrating the Security Command Class - Still only compile tested (And yes, that AES code will not work for us. Lacks some of the modes required ECB, CBCMAC and OFB)

git-svn-id: http://open-zwave.googlecode.com/svn/branches/2014-03-05-newsecurity@797 db0adee0-878e-11de-bed6-6d316fbe0868
more work on SecurityClass and also add a working AES implementation

git-svn-id: http://open-zwave.googlecode.com/svn/branches/2014-03-05-newsecurity@798 db0adee0-878e-11de-bed6-6d316fbe0868
encryption/decryption and Message Authentication Code is done. Recieved Encrypted Messages are sent to the relevent Command Classes. Sending is only partially implemented (Encryption Routine is done, but don't reroute outgoing messages from Secured Command Classes yet). Network Key Set is not done yet (need to hook into AddNode in the Driver Class) CommandsSupportedReport is not implemented

git-svn-id: http://open-zwave.googlecode.com/svn/branches/2014-03-05-newsecurity@800 db0adee0-878e-11de-bed6-6d316fbe0868
fix SIS support

git-svn-id: http://open-zwave.googlecode.com/svn/trunk@801 db0adee0-878e-11de-bed6-6d316fbe0868
integrate the Security Command Class into our QueryStage and setup Secured Command Classes once we get a report. We need to stop NONCE reports from advancing our QueryStage during discovery though, so things a bit broken right now

git-svn-id: http://open-zwave.googlecode.com/svn/branches/2014-03-05-newsecurity@802 db0adee0-878e-11de-bed6-6d316fbe0868
fix issue 310 and update ChangeLog

git-svn-id: http://open-zwave.googlecode.com/svn/branches/2014-03-05-newsecurity@803 db0adee0-878e-11de-bed6-6d316fbe0868
The Security Command Class is working! Added a very simple DoorLock Command Class to demonstrate it. We still have to do SecureInclusion support, but as long as your device is already setup then this should work. See mailing list for Instructions

git-svn-id: http://open-zwave.googlecode.com/svn/branches/2014-03-05-newsecurity@804 db0adee0-878e-11de-bed6-6d316fbe0868
make sure we store the isSecured Value in each Command Class in the zwcfg file

git-svn-id: http://open-zwave.googlecode.com/svn/branches/2014-03-05-newsecurity@805 db0adee0-878e-11de-bed6-6d316fbe0868
Secure Network Inclusion is done... Must use the Driver Interface to add Nodes currently

git-svn-id: http://open-zwave.googlecode.com/svn/branches/2014-03-05-newsecurity@806 db0adee0-878e-11de-bed6-6d316fbe0868
add the NetworkKey to the Options.xml file and parse it correctly.

git-svn-id: http://open-zwave.googlecode.com/svn/branches/2014-03-05-newsecurity@809 db0adee0-878e-11de-bed6-6d316fbe0868
update include paths and a few Windows Fixes as well as updating using correct types to help eleminate warnings (Based on Svante Karlsson work)

git-svn-id: http://open-zwave.googlecode.com/svn/branches/2014-03-05-newsecurity@810 db0adee0-878e-11de-bed6-6d316fbe0868
Update VS2010 Build Files, and fix a few windows build errors.

git-svn-id: http://open-zwave.googlecode.com/svn/branches/2014-03-05-newsecurity@811 db0adee0-878e-11de-bed6-6d316fbe0868
add some additional messages to try to figure out why we don't enter secure inclusion mode when adding new nodes

git-svn-id: http://open-zwave.googlecode.com/svn/branches/2014-03-05-newsecurity@812 db0adee0-878e-11de-bed6-6d316fbe0868
Yale Door Locks (Assa Abloy) seem to send 2 SchemeReport's. Add a check so we ignore subsequent SchemeReports after the initial one, as this can screw up the NetworkKey Set (we send one based on Scheme0, then reset our Key to the new Key, and then because of the 2nd SchemeReport, we end up sending a second NetworkKey set with essentially garbage as the new Key. Also print out the TinyXML error if we fail to parse the options.xml file

git-svn-id: http://open-zwave.googlecode.com/svn/branches/2014-03-05-newsecurity@813 db0adee0-878e-11de-bed6-6d316fbe0868
fix two compile errors on gcc 4.8.x

git-svn-id: http://open-zwave.googlecode.com/svn/branches/2014-03-05-newsecurity@814 db0adee0-878e-11de-bed6-6d316fbe0868
Whoever would have thought that Door Locks can be so complicated./getweb 1025 Completed the Door Lock Command Class V1. There is a V2 of this command class, but I don't have a Device which implements it, so this should do for now

git-svn-id: http://open-zwave.googlecode.com/svn/branches/2014-03-05-newsecurity@815 db0adee0-878e-11de-bed6-6d316fbe0868
Some Devices (Yale again) list the security command class in the SupportedReport message - indicating the device would like us to Encyrpt Messages from the Security Commaand Class - Which, is kinda redundant as thats what the Security CC does anyway - So ignore these requests, and hopefully we can proceed on

git-svn-id: http://open-zwave.googlecode.com/svn/branches/2014-03-05-newsecurity@816 db0adee0-878e-11de-bed6-6d316fbe0868
Add NodeID to Security Class Log Messages, Prepend LogLevel to Log Output and Log the Version of the Library when we start up

git-svn-id: http://open-zwave.googlecode.com/svn/branches/2014-03-05-newsecurity@817 db0adee0-878e-11de-bed6-6d316fbe0868