debian man page for shishi_keys_from_keytab_mem

Query: shishi_keys_from_keytab_mem

OS: debian

Section: 3

Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar

shishi_keys_from_keytab_mem(3)					      shishi					    shishi_keys_from_keytab_mem(3)

NAME
shishi_keys_from_keytab_mem - API function
SYNOPSIS
#include <shishi.h> int shishi_keys_from_keytab_mem(Shishi * handle, const char * data, size_t len, Shishi_keys ** outkeys);
ARGUMENTS
Shishi * handle shishi handle as allocated by shishi_init(). const char * data constant memory buffer with keytab of len size. size_t len size of memory buffer with keytab data. Shishi_keys ** outkeys pointer to key set that will be allocated and populated, must be deallocated by caller on succes.
DESCRIPTION
Create a new key set populated with keys from a MIT keytab data structure read from a memory block. The format of keytab's is proprietary, and this function support the 0x0501 and 0x0502 formats. See the section The MIT Kerberos Keytab Binary File Format in the Shishi manual for a description of the reverse-engineered format.
RETURNS
Returns SHISHI_KEYTAB_ERROR if the data does not represent a valid keytab structure, and SHISHI_OK on success.
REPORTING BUGS
Report bugs to <bug-shishi@gnu.org>.
COPYRIGHT
Copyright (C) 2002-2010 Simon Josefsson. Copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the copyright notice and this notice are preserved.
SEE ALSO
The full documentation for shishi is maintained as a Texinfo manual. If the info and shishi programs are properly installed at your site, the command info shishi should give you access to the complete manual. shishi 1.0.1 shishi_keys_from_keytab_mem(3)
Related Man Pages
shishi_authenticator_add_random_subkey(3) - debian
shishi_keys_add_keytab_mem(3) - debian
shishi_keys_from_keytab_mem(3) - debian
shishi_keys_from_keytab_file(3) - debian
shishi_tkts_add_ccache_mem(3) - debian
Similar Topics in the Unix Linux Community
using case to do this might be a bad idea?
Identifying the file completion