Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

libsasl(3lib) [opensolaris man page]

libsasl(3LIB)							Interface Libraries						     libsasl(3LIB)

NAME
libsasl - simple authentication and security layer library SYNOPSIS
cc [ flag... ] file... -lsasl [ library... ] #include <sasl/sasl.h> #include <sasl/prop.h> #include <sasl/saslutil.h> DESCRIPTION
SASL is a security framework used by connection-oriented network applications primarily for authentication. Another way to describe SASL is that it is a glue layer between a network application and some security mechanisms that allow applications to authenticate each other and provide additional security services such as data encryption. As a glue layer, SASL hides the interface specifics of the security mechanism from the application, which allows greater portability and flexibility as new security mechanisms are implemented. SASL is simi- lar to the GSS-API in that it provides a layer of abstraction between an application and one or more security mechanisms. libsasl provides both an API for applications and an SPI for various plug-ins. To link with this library, specify -lsasl on the cc command line. INTERFACES
The shared object libsasl.so.1 and associated include files provide the public interfaces defined below. The *_t interfaces are function prototypes for callbacks that are defined in the public SASL header files. While libsasl provides default versions for some of the call- backs, this structure allows an application to define its own version of the some of the callback functions. See Intro(3) for additional information on shared object interfaces. prop_clear prop_dispose prop_dup prop_erase prop_format prop_get prop_getnames prop_new prop_request prop_set prop_setvals sasl_authorize_t sasl_auxprop sasl_auxprop_add_plugin sasl_auxprop_getctx sasl_auxprop_request sasl_canon_user_t sasl_canonuser_add_plugin sasl_chalprompt_t sasl_checkapop sasl_checkpass sasl_client_add_plugin sasl_client_init sasl_client_new sasl_client_plug_init_t sasl_client_start sasl_client_step sasl_decode sasl_decode64 sasl_dispose sasl_done sasl_encode sasl_encode64 sasl_encodev sasl_erasebuffer sasl_errdetail sasl_errors sasl_errstring sasl_getcallback_t sasl_getopt_t sasl_getpath_t sasl_getprop sasl_getrealm_t sasl_getsecret_t sasl_getsimple_t sasl_global_listmech sasl_idle sasl_listmech sasl_log_t sasl_server_add_plugin sasl_server_init sasl_server_new sasl_server_plug_init_t sasl_server_start sasl_server_step sasl_server_userdb_checkpass_t sasl_server_userdb_setpass_t sasl_set_alloc sasl_set_mutex sasl_seterror sasl_setpass sasl_setprop sasl_utf8verify sasl_verifyfile_t sasl_version FILES
/usr/lib/libsasl.so.1 shared object ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWlibsasl | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
Intro(3), attributes(5), SunOS 5.11 27 Oct 2003 libsasl(3LIB)

Check Out this Related Man Page

sasl_callbacks(3)						  SASL man pages						 sasl_callbacks(3)

NAME
sasl_callbacks - How to work with SASL callbacks SYNOPSIS
#include <sasl/sasl.h> DESCRIPTION
sasl_callbacks are used when the application needs some information from the application. Common reasons are getting for getting usernames and passwords. A client MUST specify what callbacks they support in the sasl_client/server_init() or sasl_client/server_new() calls. If an authentication mechanism needs a callback that the application does not state it supports it cannot be used. If a callback has an id parameter that should be checked to make sure you are giving the appropriate value. If an application is using the client side of the library functions to handle the callbacks are not necessary. Instead the application may deal with callbacks via SASL_INTERACT's. See sasl_client_start/step() for more information. The list of callbacks follows: Common Callbacks sasl_getopt_t Get an option value sasl_log_t Log message handler sasl_getpath_t Get path to search for plugins (e.g. SASL mechanisms) sasl_verifyfile_t Verify files for use by SASL sasl_canon_user_t Username canonicalization function. Client-only Callbacks sasl_getsimple_t Get user/language list sasl_getsecret_t Get authentication secret sasl_chalprompt_t Display challenge and prompt for response sasl_getrealm_t Get the realm for authentication Server-only Callbacks sasl_authorize_t Authorize policy callback sasl_server_userdb_checkpass_t verify plaintext password sasl_server_userdb_setpass_t set plaintext password sasl_getconfpath_t Get path to search for SASL configuration file (server side only). New in SASL 2.1.22. RETURN VALUE
SASL callback functions should return SASL return codes. See sasl.h for a complete list. SASL_OK typically indicates success. CONFORMING TO
RFC 4422 SEE ALSO
sasl(3), sasl_errors(3), sasl_authorize_t(3), sasl_log_t(3), sasl_getpath_t(3), sasl_getconfpath_t(3), sasl_verifyfile_t(3), sasl_canon_user_t(3), sasl_getsimple(3), sasl_getsecret_t(3), sasl_chalprompt_t(3), sasl_getrealm_t(3), sasl_authorize_t(3), sasl_server_userdb_checkpass_t(3), sasl_server_userdb_setpass_t(3) SASL
12 February 2006 sasl_callbacks(3)
Man Page

Featured Tech Videos