From 33a9b234e7087f573ef08cd7318c6497ba08b439 Mon Sep 17 00:00:00 2001 From: Cy Schubert Date: Fri, 7 Jul 2017 17:03:42 +0000 Subject: Import MIT KRB5 1.15.1, which will gracefully replace KTH Heimdal. The tarball used in this import is the same tarball used in ports/krb5-115 r435378. Obtained from: http://web.mit.edu/kerberos/dist/ Thanks to: pfg (for all your tireless behind-the-scenes effort) --- doc/ccapi/html/structcc__data.html | 94 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 94 insertions(+) create mode 100644 doc/ccapi/html/structcc__data.html (limited to 'doc/ccapi/html/structcc__data.html') diff --git a/doc/ccapi/html/structcc__data.html b/doc/ccapi/html/structcc__data.html new file mode 100644 index 000000000000..346f6a41d616 --- /dev/null +++ b/doc/ccapi/html/structcc__data.html @@ -0,0 +1,94 @@ + + +Credentials Cache API : cc_data Struct Reference + + + + +

cc_data Struct Reference
+ +[cc_credentials_t Overview] +

Detailed Description

+The CCAPI data structure. This structure is similar to a krb5_data structure. In a v5 credentials structure, cc_data structures are used to store tagged variable-length binary data. Specifically, for cc_credentials_v5.ticket and cc_credentials_v5.second_ticket, the cc_data.type field must be zero. For the cc_credentials_v5.addresses, cc_credentials_v5.authdata, and cc_credentials_v5.keyblock, the cc_data.type field should be the address type, authorization data type, and encryption type, as defined by the Kerberos v5 protocol definition. +

+

Data Fields

+ +

Field Documentation

+

+ + + + +
+ + + + +
cc_uint32 type
+
+ + + + + +
+   + + +

+The type of the data as defined by the krb5_data structure.

+

+ + + + +
+ + + + +
cc_uint32 length
+
+ + + + + +
+   + + +

+The length of data.

+

+ + + + +
+ + + + +
void* data
+
+ + + + + +
+   + + +

+The data buffer.

+

Generated on Tue Oct 2 17:16:06 2007 for Credentials Cache API by  + +doxygen 1.4.6
+ + -- cgit v1.3