RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 625913 - changing system time could cause credentials expiration
Summary: changing system time could cause credentials expiration
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: polkit
Version: 6.1
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Miloslav Trmač
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks: 662543
TreeView+ depends on / blocked
 
Reported: 2010-08-20 19:21 UTC by Tomas Pelka
Modified: 2014-04-03 14:36 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-04-03 14:36:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
FreeDesktop.org 29712 0 None None None Never

Description Tomas Pelka 2010-08-20 19:21:23 UTC
Description of problem:
Changing system time through clock-applet could cause credentials expiration, which means the credentials are always remembered like 5 minutes or so but in this case not.
Make sence when I change time forwards, but wondering what will happen when I change time backwards. Will credentials also extend its expiration time?   


Version-Release number of selected component (if applicable):
polkit-0.96-2.el6 
polkit-gnome-0.96-3.el6 
polkit-desktop-policy-0.96-2.el6


How reproducible:
100%

Steps to Reproduce:
1. Right-client clock applet
2. Select 'Time Settings'
3. Adjust time and select 'Set System Time...'
4. Enter root password as prompted by polkit
5. Repeat steps 2.-4. several times, setting the clock both forward and backward.

  
Actual results:
Polkit do not remember crendentials when we change system time. 

Expected results:
If possible polkit should be time independent, in this special case.

Additional info:

Comment 3 RHEL Program Management 2011-01-07 15:57:41 UTC
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.

Comment 6 Siddharth Nagar 2014-04-03 14:36:00 UTC
This will be resolved in the next major version of RHEL (RHEL 7). The patch to correctly fix this is too intrusive for RHEL 6.


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