Zafer Balkan

Wazuh is a fork of OSSEC and is being actively maintained. Therefore, adding wazuh-agent to the accepted malware and rootkit detection list seems feasible. https://documentation.wazuh.com/current/user-manual/capabilities/anomalies-detection/index.html https://documentation.wazuh.com/current/pci-dss/rootkit-detection.html

RstrtMgr.dll is a newer component than Windows XP. AFAIK, it started with Windows 7 but it might be Vista. That needs some clarification. Therefore, it's not possible to solve this...

In current scenario, using Laurel requires reading `/var/log/laurel/audit.log` using json decoder. But there is no rule that matches laurel generated auditd logs. I started implementing them but failed to translate...

Do we have this in the latest version?

@healingbrew Hi. I have a question. Let's say I typed something like `cd "c:\Users\Some User\Desktop\Some Path Containing Spaces"`. Then the implementation would only care the quoted string. It might be...

In my case, I got the error when I used Shared connection Mode. But when I tried Direct Connection Mode, I managed to connect to the database.

Since SHA1 class is not FIPS compliant but HMACSHA1 is, changing [the line](https://github.com/mbdavid/LiteDB/blob/1e014473976c779e94dccad7664266c748b4e945/LiteDB/Engine/FileReader/Legacy/AesEncryption.cs#L73) from ```csharp var sha = SHA1.Create(); ``` to ```csharp var sha = new HMACSHA1(); ``` might suffice....

Hi @okynos, Let me check it out. Thank you for the review. Can you tell me which distribution did you try?

Ok. No need for an information. It was a silly issue causing recursion.

Closed for the sake of https://github.com/wazuh/wazuh-packages/pull/1824