Bug 427789

Summary: krb5 password changing uses incorrect sequence numbers for every server but the first
Product: Red Hat Enterprise Linux 5 Reporter: Nalin Dahyabhai <nalin>
Component: krb5Assignee: Nalin Dahyabhai <nalin>
Status: CLOSED ERRATA QA Contact: Brian Brock <bbrock>
Severity: low Docs Contact:
Priority: urgent    
Version: 5.1CC: jplans
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: GSSApproved
Fixed In Version: RHBA-2008-0381 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-05-21 15:28:32 UTC Type: ---
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:    
Bug Blocks: 436468    
Attachments:
Description Flags
candidate patch which fixes this for me none

Description Nalin Dahyabhai 2008-01-07 16:11:59 UTC 
Description of problem:
When the libkrb5 password-change routines generate a set-password or
change-password request, they do so in a way that the sequence number included
in password-change requests destined for any server after the first are incorrect.

Version-Release number of selected component (if applicable):
1.6.1

How reproducible:
Always

Steps to Reproduce:
1. Set multiple 'kpasswd_server' values for your realm in krb5.conf, with one
   which is known-good listed second (or third, or in any position except the
   first).
2. Run 'kpasswd' to attempt to change your password.
  
Actual results:
You'll get a decryption error from the server.

Expected results:
Not the error.

Additional information:
After we solve the client-doesn't-try-to-change-passwords-over-TCP problem, we
hit this when the client attempts to connect to the password-change service over
TCP.  My Windows Server 2003 box seems to ignore this, but it crops up with an
MIT server (heck, our own corporate server) and the FreeIPA kpasswd server.
Comment 1 Nalin Dahyabhai 2008-01-07 16:11:59 UTC 
Created attachment 290971 [details]
candidate patch which fixes this for me
Comment 10 errata-xmlrpc 2008-05-21 15:28:32 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2008-0381.html