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

Btrfs #102

Closed
DLGolden opened this issue Apr 11, 2017 · 7 comments
Closed

Btrfs #102

DLGolden opened this issue Apr 11, 2017 · 7 comments

Comments

@DLGolden
Copy link

It would appear that at some point, btrfs support got lost. Yesterday I tried the 2.0 wazuh branch and root check was alerting "Link count does not match number of files". Today I went back to the master branch and I'm getting the same thing. This is on openSUSE Leap 42.2.

The last one that I have working is the old ossec-wazuh-master dated September 24, 2016.

@DLGolden
Copy link
Author

I will revert to the September 24, 2016 ossec-wazuh-master until this is resolved.

Dennis

@vikman90
Copy link
Member

vikman90 commented Apr 11, 2017

Hi @DLGolden,

this is actually a feature inherited from OSSEC, discussed at this pull request: ossec/ossec-hids#950.

The thing is that the BTRFS file system does not perform directory counting like other file systems such ext4, so that checks were always resulting in alerts (false positives). This is why BTRFS was excluded from system directories checks.

Best regards.

@DLGolden
Copy link
Author

DLGolden commented Apr 11, 2017 via email

@vikman90
Copy link
Member

Hi,

I re-checked it again, you are absolutely right. The problem was that Rootcheck did a comparison between a signed and an unsigned integer to decide whether skip or not the directory, this made the function to fail in any case.

It was produced when fixing another issue for i386: e48713e

Solved at Master branch: ee49f12

Thank you very much for notifying us. I hope it work for you. Please test it and close this issue if it works as expected.

Best regards, and thank you again.

@DLGolden
Copy link
Author

DLGolden commented Apr 12, 2017 via email

@vikman90
Copy link
Member

The branch 2.0 is the release candidate, we are doing some testing and will decide whether update this branch for the release 2.0 or leave these changes for the next version (maybe 2.0.1).

Best regards.
Victor.

@DLGolden
Copy link
Author

I'll just stay with master then. Thanks for your quick response.

Dennis

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants