Bug 599544 - Retain old password on machine password changes
Retain old password on machine password changes
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: samba (Show other bugs)
All Linux
low Severity high
: rc
: ---
Assigned To: Guenther Deschner
Depends On:
  Show dependency treegraph
Reported: 2010-06-03 09:44 EDT by Simo Sorce
Modified: 2011-11-23 10:59 EST (History)
3 users (show)

See Also:
Fixed In Version: samba-3.5.2-63.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-10 16:33:17 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Samba Project 7099 None None None Never

  None (edit)
Description Simo Sorce 2010-06-03 09:44:11 EDT
Description of problem:
When a machine changes its password, it need to retain the old one in order to be able to accept kerberos tickets released to clients before the password change occurred. Otherwise clients will be incorrectly denied access causing errors.

Upstream has a non invasive patch that solves this issue in bug 7099.
Comment 1 RHEL Product and Program Management 2010-06-03 10:03:18 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
Comment 2 Guenther Deschner 2010-06-03 10:24:29 EDT
adding upstream bug url
Comment 7 releng-rhel@redhat.com 2010-11-10 16:33:17 EST
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

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