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.

Sign up for GitHub

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

Jump to bottom

Add test to check access to files monitored by FIM while Wazuh has them open #697

Closed
jesusjimsa opened this issue May 8, 2020 · 3 comments · Fixed by #705
Closed

Add test to check access to files monitored by FIM while Wazuh has them open #697

jesusjimsa opened this issue May 8, 2020 · 3 comments · Fixed by #705
Assignees
@Deblintrake09
Labels
feature/fim

Comments

@jesusjimsa
Copy link
Contributor

jesusjimsa commented May 8, 2020 •
edited
Loading

Description

This test must monitor a large file (1 GB), perform a modification in the file and rename/delete it. No error should appear in the log and the rename/delete operation should be performed correctly.

Modes

  • scheduled
  • realtime
  • whodata

Platforms

  • Windows
  • Linux
  • macOS
  • Solaris
@jesusjimsa jesusjimsa self-assigned this May 8, 2020
@jesusjimsa jesusjimsa changed the title Add test for permission in large files Add test for access in large files May 8, 2020
@jesusjimsa jesusjimsa changed the title Add test for access in large files Add test for access in files being modified May 8, 2020
@jesusjimsa jesusjimsa changed the title Add test for access in files being modified Add test to check access to files monitored while performing file hashing May 8, 2020
@jesusjimsa jesusjimsa changed the title Add test to check access to files monitored while performing file hashing Add test to check access to files monitored by FIM while Wazuh has them open May 8, 2020
@bah07 bah07 added this to the Sprint 111 - Core milestone May 8, 2020
@jesusjimsa
Copy link
Contributor Author

The test is working correctly in Linux.

When executing the test in Windows, it uses a lot of memory. If the test gets to the limit of the available memory in the system, a MemoryError will be raised. To be executed without any problem, the machine must have at least 4 GB of memory.

@jesusjimsa jesusjimsa mentioned this issue May 11, 2020
Merged
@jesusjimsa
Copy link
Contributor Author

The MemoryError has been solved by writing to the file in chunks instead of the entire file at once. After fixing this, the test can be run in systems with 2 GB.

@Molter73 Molter73 mentioned this issue May 13, 2020
Merged
8 tasks
@jesusjimsa jesusjimsa removed their assignment Jan 15, 2021
@jmv74211 jmv74211 removed the core/fim label Jun 22, 2021
@damarisg damarisg mentioned this issue Nov 16, 2021
Closed
4 tasks
@Deblintrake09
Copy link
Contributor

Status
Reviewing test structure and analyzing fixes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Deblintrake09 Deblintrake09

Labels
feature/fim
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add test to check if files can be accessed while FIM has them opened wazuh/wazuh-qa
5 participants
@damarisg @bah07 @Deblintrake09 @jesusjimsa @jmv74211