Planning and Configuring HP DCE 1.8

26 Chapter1
About HP DCE/9000 Version 1.8
Interoperability and Compatibility
3. If using Integrated Login, log out and log in.
If a statically-linked HP DCE 1.7 application purges a login context
(via sec_login_purge_context) which an HP DCE 1.8 application
had created or refreshed, one of the credential files will not be deleted
from the disk. This file is located in
/var/opt/dce/security/creds directory. The file name will
consist of the unique credential cache ID associated with the login
context and a ".data.db" suffix. Administrators may remove this file
manually if they wish.
For information about the U.S./Canada version of HP DCE, see the HP
DCE/9000 Version 1.7 U.S./Canda Version Release Note.
Source Code Compatibility with Previous HP DCE
Releases
There are no known source code incompatibilities between HP DCE 1.8
and previous releases.
Interoperability of the DES Version
The DES version of DCE is interoperable with any DCE version that has
been built with the DES code omitted (instead of hidden). Some DCE
ports from other vendors were built in this way in order to meet U.S.
export requirements. If you are running a DCE port from another
vendor, check with that vendor for details.
Kerberos Authentication Protocol Compatibility
The DCE Security authentication service implements Kerberos Version
5. DCE Security does not provide backward compatibility support for
Kerberos Version 4.
DCE Support for Kerberos Applications and
Configuration Notes
HP DCE 1.8 makes available enhanced configuration features specific to
Kerberos Version 5. Configuration with dce_config has been updated to
do the following for either a security server or client:
• Create a host principal, account and keytab entry for secure BSD