Bug 146122 - Add laus to RedHat 4.0
Summary: Add laus to RedHat 4.0
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: laus
Version: 3.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Charlie Bennett
QA Contact: Jay Turner
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-01-25 15:40 UTC by Wendy Wilz
Modified: 2015-01-08 00:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-01-31 22:34:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Wendy Wilz 2005-01-25 15:40:43 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 4.0; 
Q312461)

Description of problem:
Please add the latest laus rpm to RedHat Enterprise 4.0.  It is not 
part of the beta software available RedHat Enterprise Linux WS 3.90 
(Nahant). 

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


How reproducible:
Always

Steps to Reproduce:
1.Download RedHat WS 4.0 beta
2. Load
3. rpm -q | grep laus
    

Additional info:

According to DISA, I must have auditing running.

Comment 1 Charlie Bennett 2005-01-31 15:27:05 UTC
Laus was in interim solution brought into RHEL3 which was never accepted by the
upstream Linux kernel development team (Torvalds, etc.).

RHEL4 is getting a new Auditing subsystem which is compatible with the new
SELinux subsystem.  The implementation of this auditing subsystem is not fully
functional with the initial release of RHEL4.  We expect substantial
functionality to be in place for U1 and a fully polished and certifiable
implementation to be available in U2.

The new auditing subsystem has the full blessing of the upstream kernel
community and is part of the globally available 2.6 kernels.  Development on
this subsystem is being done as a comminity project with the heavy participation
of IBM, the NSA and others.  We regret that the task of implementing Laus in
RHEL4 would greatly detract from work on the new subsystem and ask you to
continue with RHEL3 until we've gotten RHEL4 auditing fully operational.


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