Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix reading of Windows platform in 64 bits systems #832

Merged
merged 2 commits into from Jun 27, 2018

Conversation

chemamartinez
Copy link
Contributor

This PR solves the issue #825.

The Windows agent reads the OS information from the registry when it starts, sending the data to the manager and Kibana later.

By default, it was being read the 32 bits registry, even if the Windows is a 64 bits system.

The root cause of that issue is that in 64 bits Windows 10 Pro, there exists an inconsistency in both registry views. In the 32 bits registry, the ProductName key read from HKLM\Software\ Wow6432Node\Microsoft\WindowsNT\CurrentVersion contains the value Windows 10 Enterprise, while the equivalent value for the 64 bits view is Windows 10 Pro.

It has been added a flag when opening the registry to read the 64 bits registry on 64 bits Operating Systems. This is the new information retrieved by the Wazuh agent:

 2018/06/22 15:49:34 ossec-agent: INFO: Windows version is 6.0 or newer. (Microsoft Windows 10 Pro [Ver: 10.0.17134] - Wazuh v3.3.2).

Regards.

@chemamartinez chemamartinez merged commit 9e71b49 into 3.3 Jun 27, 2018
Wazuh TBD automation moved this from In review to Done Jun 27, 2018
@chemamartinez chemamartinez deleted the fix-win-platform branch June 27, 2018 14:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants