Bug 1508878

Summary: Rebase USBGuard to latest upstream
Product: Red Hat Enterprise Linux 7 Reporter: Daniel Kopeček <dkopecek>
Component: usbguardAssignee: Daniel Kopeček <dkopecek>
Status: CLOSED ERRATA QA Contact: Jiri Jaburek <jjaburek>
Severity: unspecified Docs Contact: Mirek Jahoda <mjahoda>
Priority: unspecified    
Version: 7.4CC: dapospis, dkopecek, jjaburek, mjahoda, mthacker
Target Milestone: rcKeywords: Rebase, Triaged
Target Release: 7.6   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: usbguard-0.7.4-1.el7 Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
_usbguard_ rebased to version 0.7.4 The _usbguard_ packages have been rebased to upstream version 0.7.4. This version provides a number of bug fixes and enhancements over the previous version, most notably: * The *usbguard-daemon* now exits with an error if it fails to open a logging file or an audit event file. * The present device enumeration algorithm is now more reliable. Enumeration timeouts no longer cause the *usbguard-daemon* process to exit. * The "usbguard watch" command now includes the "-e" option to run an executable for every received event. The event data is passed to the executable through environment variables.
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-30 11:27:17 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:

Description Daniel Kopeček 2017-11-02 12:36:07 UTC
Rebase USBGuard to latest version to bring in new features like:
 - SELinux support
 - UI enhancements
 - GUI support
 - documentation enhancements

Comment 8 errata-xmlrpc 2018-10-30 11:27:17 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/RHEA-2018:3235