1.. highlight:: c 2 3.. _krb5-crypto-iov-struct: 4 5krb5_crypto_iov 6=============== 7 8.. 9.. c:type:: krb5_crypto_iov 10.. 11 12Structure to describe a region of text to be encrypted or decrypted. 13 14The *flags* member describes the type of the iov. The *data* member points to the memory that will be manipulated. All iov APIs take a pointer to the first element of an array of krb5_crypto_iov's along with the size of that array. Buffer contents are manipulated in-place; data is overwritten. Callers must allocate the right number of krb5_crypto_iov structures before calling into an iov API. 15 16Declaration 17------------ 18 19typedef struct _krb5_crypto_iov krb5_crypto_iov 20 21 22Members 23--------- 24 25 26.. c:member:: krb5_cryptotype krb5_crypto_iov.flags 27 28 iov type (see KRB5_CRYPTO_TYPE macros) 29 30 31.. c:member:: krb5_data krb5_crypto_iov.data 32 33 34 35 36