Bug 591359 - Typo in /usr/share/doc/audit-x.x.x/stig.rules
Summary: Typo in /usr/share/doc/audit-x.x.x/stig.rules
Alias: None
Product: Fedora
Classification: Fedora
Component: audit (Show other bugs)
(Show other bugs)
Version: 12
Hardware: All Linux
Target Milestone: ---
Assignee: Steve Grubb
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-12 01:44 UTC by Morgan Weetman
Modified: 2010-11-04 20:03 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-04 20:03:50 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Morgan Weetman 2010-05-12 01:44:40 UTC
Description of problem:
Typo in /usr/share/doc/audit-x.x.x/stig.rules

Version-Release number of selected component (if applicable):
Noticed in F12, also present in RHEL5.3

How reproducible:
View /usr/share/doc/audit-x.x.x/stig.rules

Steps to Reproduce:
1. grep time-change /usr/share/doc/audit-2.0.4/stig.rules 

Actual results:
-a always,exit -F arch=b32 -S adjtimex -S settimeofday -S stime -k time-change
-a always,exit -F arch=b64 -S adjtimex -S settimeofday -k time-change
#-a always,exit -F arch=b32 -S clock_settime -k time-change
#-a always,exit -F arch=b64 -S clock_settime -k time-change
-w /etc/localtime -p wa -k time-change

Expected results:
-a exit,always -F arch=b32 -S adjtimex -S settimeofday -S stime -k time-change
-a exit,always -F arch=b64 -S adjtimex -S settimeofday -k time-change
#-a exit,always -F arch=b32 -S clock_settime -k time-change
#-a exit,always -F arch=b64 -S clock_settime -k time-change
-w /etc/localtime -p wa -k time-change

Additional info:

Comment 1 Steve Grubb 2010-05-12 13:52:13 UTC
I'm still trying to figure out what is wrong. It looks like you list 5 rules in actual and expected results, the key is teh same on each one, the syscalls are the same, the watch is the same.

Comment 2 Morgan Weetman 2010-05-12 23:57:47 UTC
(In reply to comment #1)
> I'm still trying to figure out what is wrong. It looks like you list 5 rules in
> actual and expected results, the key is teh same on each one, the syscalls are
> the same, the watch is the same.    

Sorry ... the list and action are in the wrong order 'always,exit' should be 'exit,always'

Comment 3 Steve Grubb 2010-05-13 01:40:04 UTC
Ok. The order for that field does not matter. Auditctl will accept things in either order. I suppose I could arrange it for consistency, but I wouldn't call it a bug unless auditctl reports an error.

Comment 4 Morgan Weetman 2010-05-13 02:54:39 UTC
No problems, just caused a little confusion as it didn't match the man page


Comment 5 Bug Zapper 2010-11-03 15:03:12 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 6 Steve Grubb 2010-11-04 20:03:50 UTC
This was fixed in an upstream commit:

It will be in audit-2.0.6 when that is released.

Note You need to log in before you can comment on or make changes to this bug.