...

• Fixed intermittent locking issue when stopping the MSSQL service from the Service Control Manager.
• Added a warning message that is displayed This change affects the warning messages that are display when protocol for destination is set to TCP or TLS for web UI port 6161 as it can slow down the agent receiving log messages, which will be ignored on the web interface. In high volume environments the agent may appear to hang as a result. As it is not a recommended configuration this will now show as a warning if the agent is configured in this way. In general sending logs to the localhost is only used for testing and only used when its UDP protocol so the logs are discarded. Any real destination should use a real hostname or IP address and not localhost. This change does not affect any other functionality.

V5.1.2

Bug Fixes

• Removed CacheSizeSet setting from installer script.

• Added missing registry values in installer script.

...

• Notification and warning on Snare agents has been changed to to allow syslog_5424 format on port 514. As a result of this change, notification and warning will no longer appear for valid syslog format's when using port 514.
• Fix a potential for memory corruption of event data being sent via TCP, TLS or UDP when under very heavy loads.
• There was an issue in previous release of the snare agent where it was not properly handling the objectives during upgrade to latest release. Due to this issue, objectives may not be available after upgrade. This issue is fixed in this release and now snare properly handles the objectives during upgrade and all objectives are available after upgrade.
• Snare agent warning and notification messages has been changed to issue warning for selecting non-TAB delimiter for SNARE format(Snare Server destination). As a result of this change, new warning's will be issued when non-TAB delimited for SNARE format (for Snare Server destination) is selected.
• There was a debug logging issue in previous release of SnareMSSQL agent. Due to this issue, SnareMSSQL was not able to properly show the log messages on console if run from console. The fix ensures SnareMSSQL logs all the messages to console window as per input parameter -d when run from console. (e.g. snaremssql -c -d SAM:trace > mysnare.log 2>&1 )
• There was an issue with the uninstaller of the SnareMSSQL agent. Due to this issue uninstaller was not properly cleaning the registry of the SnareMSSQL agent. This issue is fixed in this release and now uninstaller properly cleans the registry during uninstall.
• There was in issue the way SnareMSSQL was saving/updating the objective. Due to this issue, an objective would not save correctly when 'Including SELECT' check box was checked on objective page. This issue is fixed in this release and now SnareMSSQL properly save the value of 'Including SELECT' checkbox.
• There was an installing issue in previous release of SnareMSSQL where installation was made using .inf file on machines that are part of Windows Cluster or machines running with Windows Server 2016. Due to these installation issues, SnareMSSQL installation might fail or objectives might fail to load from .inf file. These issues are fixed in this release. Now SnareMSSQL handles cluster installation as well as properly supports Windows Server 2016.
• There was an issue in previous release of SnareMSSQL where setting 'Use plain text objective data' under General Configuration was not working. Due to this issue objectives were not stored in plain text even when this option is checked. This issue is fixed in this release and now SnareMSSQL properly honors the setting 'Use plain text objective data' .
• Updated the validation of event types in objectives. An objective cannot be saved if at least one event type is not selected. This is to ensure that only a valid objective is saved.

...