Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 165611 - initscript shutdown, hwclock, and auditing
Summary: initscript shutdown, hwclock, and auditing
Alias: None
Product: Fedora
Classification: Fedora
Component: initscripts
Version: 4
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
: 210929 251213 (view as bug list)
Depends On:
Blocks: FC5Target
TreeView+ depends on / blocked
Reported: 2005-08-10 19:49 UTC by Steve Grubb
Modified: 2014-03-17 02:55 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-10-17 18:55:28 UTC

Attachments (Terms of Use)

Description Steve Grubb 2005-08-10 19:49:00 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050720 Fedora/1.0.6-1.1.fc3 Firefox/1.0.6

Description of problem:
With the current version of util-linux, audit, kernel, and initscripts a message is hitting the console with audit information. hwclock was patched to send an audit event as any changes to it are part of CC security targets. 

However, the audit daemon has already exited by the time hwclock sync is done during shutdown or reboot. The hwclock sync really needs to be done earlier so that it gets recorded by the audit daemon...and as a side effect...stops annoying users. I don't think it makes a big difference if the hwclock sync happens earlier does it?

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. make sure current audit, kernel, util-linux, and initscripts are installed
2. shutdown computer
3. watch console for audit event related to hwclock

Actual Results:  msg=audit(1123702797.998:1420642): user pid=4440 uid=0 auid=0 msg='hwclock: op=changing system time id=0 res=success'

Expected Results:  no messages

Additional info:

Comment 1 Bill Nottingham 2005-08-19 07:19:34 UTC
How can we be sure that more of these won't come later?

Is it possible for the audit system to disable printing to console on exit?

Comment 2 Steve Grubb 2005-08-19 11:55:24 UTC
The issue is that changes to the hardware clock is an auditable event in CAPP
and LSPP. We are missing that event because the clock sync occurs after the
audit daemon has been terminated. There may be other audit messages that hit the
screen on shutdown, but they probably aren't in the security target like hwclock

The audit daemon could do something with dmesg to quieten messages that hit the
screen, but something important not related to auditing might get suppressed.

Comment 3 Bill Nottingham 2005-10-03 21:27:32 UTC
The problem is that creating a separate script *just* for syncing the clock is
certainly way too much overkill; realistically, it's at the proper place now.

Comment 4 Steve Grubb 2005-10-03 21:42:12 UTC
I was thinking this is just re-ordering what is in /etc/rc.d/init.d/halt. That's

The reason that this needs to be done is not because of getting rid of messages
to the console (although people would like that), its about getting the sync
done while the audit damon is alive so that the event is properly recorded. All
changes to hwclock is an auditable event in CAPP security targets.

I have been considering adding this to U3 proposed since its a hole in auditing
right now.

Comment 5 Bill Nottingham 2005-10-03 21:55:14 UTC
Just moving it? You're implying that audit doesn't die when you shut down the
service, only when the killall command in halt is run?

Comment 6 Steve Grubb 2005-10-15 12:44:10 UTC
I spoke with Klaus of atsec about this bug report. He said that if we have not
wrote any code at this point, not to worry about it. He feels this is in the
nice to have category and can be explained away in Security Targets. So...if no
code has been written, this bug report can be closed.

Comment 7 Bill Nottingham 2005-10-17 18:55:28 UTC
Hasn't been changed yet, so closing.

Comment 8 Bill Nottingham 2006-10-16 17:28:27 UTC
*** Bug 210929 has been marked as a duplicate of this bug. ***

Comment 9 Need Real Name 2006-10-16 19:04:36 UTC
Well it's nice that it's closed, but it looks like something is going wrong,
which is why I files bug 210929.

The Fedora wiki states that all AVC messages for software installed by default
are blockers, so I find it odd that this gets swept under the carpet.

Comment 10 Bill Nottingham 2007-08-07 19:49:53 UTC
*** Bug 251213 has been marked as a duplicate of this bug. ***

Comment 11 Martin Jürgens 2007-08-07 20:17:18 UTC
I have the same opinion as lsof. It should be fixed as stated in the wiki.  And
more than 2 years to fix a "nice to have" bug in that all users run when
shutting down their system are a lot, honestly.

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