[139] in pc-kerberos

home help back first fref pref prev next nref lref last post

Re: Upcoming potential changes in KRBV4*.DLL

daemon@ATHENA.MIT.EDU (Theodore Ts'o)
Thu Aug 3 18:27:27 1995

Date: Thu, 3 Aug 1995 18:18:35 -0400
From: Theodore Ts'o <tytso@MIT.EDU>
To: John Gardiner Myers <jgm+@CMU.EDU>
Cc: pc-kerberos@MIT.EDU
In-Reply-To: "[138] in pc-kerberos"

   Date: Thu,  3 Aug 1995 15:20:14 -0400 (EDT)
   From: John Gardiner Myers <jgm+@CMU.EDU>

   Because the site has deployed Transarc RX-based password changing
   clients which are only capable of using the Transarc string-to-key.
   In that case, storing a MIT v4 string-to-key encoded key in the
   database will prevent the user from being able to change their
   password with a Transarc password-changing client.

Ah, OK.  In that case, you're right --- making the kadmind be able to
use the Transarc string-to-key will do the right thing.  And once those
password changing clients can be updated to use the standard password
changing clients, a single change at the kadmin server will allow those
sites to transition back to the MIT string_to_key().

						- Ted

home help back first fref pref prev next nref lref last post