Copyright (c) 2004, Sun Microsystems, Inc. All Rights Reserved.
The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
cc [ flag... ] file... -lpam [ library... ] #include <security/pam_appl.h>
Functions in this library provide routines for the Pluggable Authentication Module (PAM).
The shared object libpam.so.1 provides the public interfaces defined below. See Intro(3) for additional information on shared object interfaces.
pam_acct_mgmt | pam_authenticate |
pam_chauthtok | pam_close_session |
pam_end | pam_get_data |
pam_get_item | pam_get_user |
pam_getenv | pam_getenvlist |
pam_open_session | pam_putenv |
pam_set_data | pam_set_item |
pam_setcred | pam_start |
pam_strerror | |
shared object
configuration file
/usr/lib/security/pam_dial_auth.so.1
authentication management PAM module for dialups
/usr/lib/security/pam_rhosts_auth.so.1
authentication management PAM modules that use ruserok()
/usr/lib/security/pam_sample.so.1
sample PAM module
See attributes(5) for description of the following attributes:
ATTRIBUTE TYPE | ATTRIBUTE VALUE |
MT Level | MT-Safe with exceptions |
pvs(1), Intro(3), pam(3PAM), pam.conf(4), attributes(5), pam_authtok_check(5), pam_authtok_get(5), pam_authtok_store(5), pam_dial_auth(5), pam_dhkeys(5), pam_passwd_auth(5), pam_rhosts_auth(5), pam_sample(5), pam_unix_account(5), pam_unix_auth(5), pam_unix_session(5)
The functions in libpam are MT-Safe only if each thread within the multithreaded application uses its own PAM handle.
The pam_unix(5) module is no longer supported. Similar functionality is provided by pam_authtok_check(5), pam_authtok_get(5), pam_authtok_store(5), pam_dhkeys(5), pam_passwd_auth(5), pam_unix_account(5), pam_unix_auth(5), and pam_unix_session(5).