Commits on Apr 26, 2016

1. Fix panic when reading messages larger than 32K characters on Windows… …

   … XP and 2003.
   
   Winlogbeat was passing the size of the buffer to Windows using number of bytes, but Windows was expecting number of TCHAR's. This made Windows return that the number of TCHARs read was greater than the number that the buffer could hold. Winlogbeat used the return value to read from the buffer which caused a 'runtime error: slice bounds out of range' panic.
   
   The buffer length issue has been corrected by dividing by sizeof(TCHAR) which is 2. In addition a check has been added to verify that the return value from Windows is sane before using it to slice the buffer.

   

   andrewkroh committed Apr 26, 2016
   Configuration menu

   • View commit details
   • Copy full SHA for 90a2a90
   • Browse repository at this point

   Copy the full SHA

   90a2a90 View commit details

   Browse the repository at this point in the history