Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
The "aide -C" command fails to process a gzipped database file when the uncompressed file is exactly n*8192+11 bytes long for some n>0.
Version-Release number of selected component (if applicable):
aide-0.16-14.el8_5.1
How reproducible:
When the database size is as described, "aide -C" fails every time.
Steps to Reproduce:
It is difficult to create a database of the required size, but I have attached a contrived example.
Actual results:
The "aide -C" command fails with varying errors though usually the errors include "Trying to continue on line xx" for some xx and "db_char2line():Error while reading database"
Expected results:
The "aide -C" command should properly check the database.
Additional info:
This patch fixes the problem:
diff -ru aide-0.16/src/commandconf.c aide-0.16.modified/src/commandconf.c
--- aide-0.16/src/commandconf.c 2016-07-25 15:56:55.000000000 -0500
+++ aide-0.16.modified/src/commandconf.c 2023-07-18 08:48:11.913932324 -0500
@@ -303,6 +303,7 @@
retval=0;
buf[0]='\0';
}else {
+ buf[0]='\0';
if((retval=gzread(*db_gzp,buf,max_size))<0){
error(0,_("gzread() failed: gzerr=%s!\n"),gzerror(*db_gzp,&err));
retval=0;
Description of problem: The "aide -C" command fails to process a gzipped database file when the uncompressed file is exactly n*8192+11 bytes long for some n>0. Version-Release number of selected component (if applicable): aide-0.16-14.el8_5.1 How reproducible: When the database size is as described, "aide -C" fails every time. Steps to Reproduce: It is difficult to create a database of the required size, but I have attached a contrived example. Actual results: The "aide -C" command fails with varying errors though usually the errors include "Trying to continue on line xx" for some xx and "db_char2line():Error while reading database" Expected results: The "aide -C" command should properly check the database. Additional info: This patch fixes the problem: diff -ru aide-0.16/src/commandconf.c aide-0.16.modified/src/commandconf.c --- aide-0.16/src/commandconf.c 2016-07-25 15:56:55.000000000 -0500 +++ aide-0.16.modified/src/commandconf.c 2023-07-18 08:48:11.913932324 -0500 @@ -303,6 +303,7 @@ retval=0; buf[0]='\0'; }else { + buf[0]='\0'; if((retval=gzread(*db_gzp,buf,max_size))<0){ error(0,_("gzread() failed: gzerr=%s!\n"),gzerror(*db_gzp,&err)); retval=0;