Bug 130930 - missing syscall auditing for pread() and pwrite()
Summary: missing syscall auditing for pread() and pwrite()
Keywords:
Status: CLOSED DUPLICATE of bug 130823
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel
Version: 3.0
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Peter Martuccelli
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-08-25 20:42 UTC by Stephanie Lockwood-Childs
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:05:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Stephanie Lockwood-Childs 2004-08-25 20:42:28 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; 
T312461; LM-MS; .NET CLR 1.0.3705; .NET CLR 1.1.4322)

Description of problem:
The system calls pread() and pwrite() currently can not be audited. 
Unlike other related calls such as read(), readv(), write(), and 
writev(), these calls are not included in the list of auditable calls 
in drivers/audit/syscall.c. This is a significant hole in the 
auditing support, because it allows a way to write to sensitive files 
without the write access being logged.

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


How reproducible:
Always

Steps to Reproduce:
1. create rules to enable auditing of pwrite and pread 
in /etc/audit/filter.conf
2. enable auditing
3. run a program that uses pread or pwrite
    

Actual Results:  Access using pread or pwrite is not logged, and a 
kernel error message is generated for each time the syscall is 
used: "Filter target 0x0 not known or not supported in this context"



Expected Results:  The accesses should be logged

Additional info:

Comment 1 Ernie Petrides 2004-08-26 00:13:55 UTC

*** This bug has been marked as a duplicate of 130823 ***

Comment 2 Red Hat Bugzilla 2006-02-21 19:05:17 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


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