-
Notifications
You must be signed in to change notification settings - Fork 127
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
Object summary is empty since 2.4.3.3 update #24
Comments
Hi, |
Hi, the issue you're seeing is something I broke in 2.4.3.3 (see #19 for details ), and it's fixed in 2.4.3.4 & later. |
tripwire-2.4.3.4-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1435181 |
Works again! |
Great, glad to hear it! |
closing as resolved |
I a running TW on a CentOS 6.8
2.6.32-042stab120.5 #1 SMP Tue Oct 25 22:31:12 MSK 2016 x86_64 x86_64 x86_64 GNU/Linux
with
yum-cron.noarch 3.2.29-75.el6.centos @updates
On March 21 there was following automatic update:
#==============================================================
Package Arch Version Repository Size
#==============================================================
Updating:
tripwire x86_64 2.4.3.3-1.el6 epel 1.4 M
Ever since this update the Object summary printed after a --check is empty (modified, added, or removed files are not listed any more). The number of violations is correct and the report file shows the violating files. The cfg and pol files have not changed, although there are new versions of the txt files present.
...
Total objects scanned: 41435
Total violations found: 39
#===========================================================
Object Summary:
#===========================================================
#-------------------------------------------------------------------------------
Section: Unix File System
#-------------------------------------------------------------------------------
#-------------------------------------------------------------------------------
Rule Name: Root config files (/root)
Severity Level: 100
#-------------------------------------------------------------------------------
#===========================================================
Error Report:
#===========================================================
No Errors
#-------------------------------------------------------------------------------
The text was updated successfully, but these errors were encountered: