[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: smbk5pwd: pass change exop works, {K5KEY} check doesn't

To: Kris Maglione <bsdaemon@comcast.net>
Subject: Re: smbk5pwd: pass change exop works, {K5KEY} check doesn't
From: Howard Chu <hyc@symas.com>
Date: Sat, 02 Jul 2005 15:48:15 -0700
Cc: openldap-software@OpenLDAP.org
In-reply-to: <42C6A35F.5040504@comcast.net>
References: <42C5EB45.5010607@comcast.net> <42C646D5.6060702@symas.com> <42C6A35F.5040504@comcast.net>
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050621

Kris Maglione wrote:

 I'm sorry I didn't explain that better. I set the value back to
 {K5KEY} after the exop changed it. I've read in several places that
 "password-hash" had to be set to {CLEARTEXT} for this module to work,
 but that stored the cleartext password.

A quick Google didn't turn up any statements to this effect for me. Wherever you read that, ignore it. The password-hash should be {K5KEY} if you want the Kerberos key to be used.

--
 -- Howard Chu
 Chief Architect, Symas Corp.       Director, Highland Sun
 http://www.symas.com               http://highlandsun.com/hyc
 Symas: Premier OpenSource Development and Support

Follow-Ups:
- Re: smbk5pwd: pass change exop works, {K5KEY} check doesn't
  - From: Kris Maglione <bsdaemon@comcast.net>

References:
- smbk5pwd: pass change exop works, {K5KEY} check doesn't
  - From: Kris Maglione <bsdaemon@comcast.net>
- Re: smbk5pwd: pass change exop works, {K5KEY} check doesn't
  - From: Howard Chu <hyc@symas.com>
- Re: smbk5pwd: pass change exop works, {K5KEY} check doesn't
  - From: Kris Maglione <bsdaemon@comcast.net>

Prev by Date: Re: smbk5pwd: pass change exop works, {K5KEY} check doesn't
Next by Date: Re: smbk5pwd: pass change exop works, {K5KEY} check doesn't
Index(es):
- Chronological
- Thread