Hide Forgot
Description of problem: Problem is that the process is owned by current user, probably for a good reason, however if you have you have smart card support enabled and use the "lock_screen on card removal"-option as a security measure, it is easy for the user to kill this process and thereby kill the mechanism that controls the "lock_screen on card removal"-feature. As I point out in the beginning, there is probably a good reason for this processs to be owned and runned by the current user, however the security mechasims should be changed. If you have a policy that says that the user *must* have his card in place, otherwise the screen should be locked, that policy should not be able to be overridden by the user by killing a process. Version-Release number of selected component (if applicable): gnome-settings-daemon-2.28.2-11.el6.x86_64 How reproducible: Always Steps to Reproduce: 1. Enable "Lock on card removal"-feature. 2. Kill gnome-settings-daemon 3. Remove card. Actual results: Nothing happends at card-removal. Expected results: Screensaver activates and locks session. Additional info: This is probably not a bug in gnome-settings-daemon per say, but rather the way the smart card-local-at-removal-feature is implemented.
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative.
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available. The official life cycle policy can be reviewed here: http://redhat.com/rhel/lifecycle This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL: https://access.redhat.com/