Bug 1478888

Summary: Clevis should log privileged operations
Product: Red Hat Enterprise Linux 7 Reporter: Dmitri Pal <dpal>
Component: clevisAssignee: Nathaniel McCallum <npmccallum>
Status: CLOSED ERRATA QA Contact: Jiri Jaburek <jjaburek>
Severity: medium Docs Contact: Mirek Jahoda <mjahoda>
Priority: high    
Version: 7.4CC: herrold, jjaburek, npmccallum, rpacheco
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
_clevis_ now logs privileged operations With this update, the _clevis-udisks2_ subpackage logs all attempted key recoveries to the Audit log, and the privileged operations can be now tracked using the Linux Audit system.
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-10 18:27:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1507653    
Bug Blocks:    

Description Dmitri Pal 2017-08-07 12:51:34 UTC
Clevis UDisks2 support performs privileged operations on behalf of an unprivileged user. For the purposes of auditing, this privilege transition needs to be logged.

When this issue is addressed an audit event should show in the log as result of using clevis with a flash memory drive.

Comment 3 Nathaniel McCallum 2017-08-07 14:22:24 UTC
UDisks2 support currently logs messages to standard error for the purposes of debugging. However, we need to log all attempted key recoveries to the audit log since this recovery occurred on data obtained with elevated privileges.

Comment 16 Nathaniel McCallum 2018-01-08 15:25:46 UTC
Clarification: clevis-udisks2 does logging. Not the entire framework.

Comment 19 errata-xmlrpc 2018-04-10 18:27:23 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0985