K5Client support broken when using KClient 3.0 compatibility API?
mjv at MIT.EDU
Thu Oct 31 10:48:01 EST 2002
At 3:59 PM -0600 10/30/02, Steven Michaud wrote:
>Could using the KClient 3.0 shared libraries have broken KFM's
Accessing the KClient 3.0 APIs is done by standard system calling
conventions as opposed to the old KClient driver interface. It was
the driver compatibility interface which handled the K5Client switch.
Thus there is no support for an automatic K5Client mode when
accessing KClient through normal standard interfaces.
Eudora needed to move to the newer APIs in order to gain additional
functionality they required.
K5Client is not considered supported functionality in the KfM product.
Marshall Vale | mjv at mit.edu | Information Systems
Massachusetts Institute of Technology
More information about the krbdev