HP-UX Reference (11i v2 07/12) - 3 Library Functions A-M (vol 6)

ManualsBrandsHP ManualsSoftwareHP-UX Reference Manuals

691

692

693

694

695

696

697

698

699

700

libkrb5(3) libkrb5(3)

krb5_free_cred()

, krb5_free_pa_data()

, and krb5_free_tgt_creds()

Operating System-Speciﬁc APIs

These APIs provide an interface between the other parts of the

libkrb5 libraries and the operating sys-

tem. These include APIs to allow access to conﬁguration speciﬁc information, disk based I/O operations,

network based operations and operating system speciﬁc access APIs. Some of the common APIs are

krb5_set_config_file()

, krb5_get_default_realm()

, krb5_get_krbhst()

krb5_gen_portaddr()

, krb5_read_message()

, krb5_kuserok()

, krb5_timeofday()

and krb5_read_passwd()

Application-Speciﬁc and Miscellaneous APIs

These APIs deal with sending and receiving KRB5 protocol messages to the Kerberos server, ticket

management and miscellaneous calls. Some of the common APIs are

krb5_get_cred_from_kdc()

krb5_get_credentials()

, krb5_get_in_tkt_with_password()

, krb5_rd_rep()

krb5_mk_error()

, krb5_sendauth()

, and krb5_recvauth()

Itanium-based Systems

The Kerberos APIs have support for IPv6-enablement of application in Kerberos mode. For an application

to be v6-enabled in Kerberos mode, the application needs to obtain the v6-context by calling

krb5_init6_context()

, and send that v6-context as an argument to other Kerberos APIs. The API

krb5_init6_context()

will initialize a v6-context on an IPv6-enabled system. If the local host is not

IPv6-enabled, it returns the error code

KRB5KRB_INIT_ERR_V6 but initializes a v4-context, which

means the application will perform all the Kerberos operations in v4-mode only. During compilation of an

application that includes

<krb5.h>, the preprocessor macro, _HAVE_KRB5_IPV6_

needs to be deﬁned

for the IPv6 enablement. The address type to be used for IPv6 is

ADDRTYPE_INET6, which is deﬁned in

<krb5.h>.

WARNINGS

It is strongly recommended to use GSS-API instead of Kerberos calls. The Kerberos libraries are not

thread safe.

AUTHOR

Kerberos client libraries were developed at Massachusetts Institute of Technology. This version of the

libraries are compatible with MIT1.0, MIT1.1 and MIT1.1.1.