From 9fb9393ede4ee9d43ff841557f95ed2af7d1a15f Mon Sep 17 00:00:00 2001 From: "Andrew G. Morgan" Date: Mon, 22 Jan 2001 06:07:28 +0000 Subject: Relevant BUGIDs: 129027, 128576 Purpose of commit: new feature + documentation Commit summary: --------------- Cleaned up the handling of AUTHTOK items and pam_[gs]et_data() functions. Added more clear documentation about the pam_[gs]et_item() functions to the pam_appl and pam_modules programmer guides. --- libpam/pam_start.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'libpam/pam_start.c') diff --git a/libpam/pam_start.c b/libpam/pam_start.c index fb222d62..0e50bb40 100644 --- a/libpam/pam_start.c +++ b/libpam/pam_start.c @@ -29,6 +29,11 @@ int pam_start ( return (PAM_BUF_ERR); } + /* Mark the caller as the application - permission to do certain + things is limited to a module or an application */ + + __PAM_TO_APP(*pamh); + if (service_name) { char *tmp; @@ -92,11 +97,6 @@ int pam_start ( /* According to the SunOS man pages, loading modules and resolving * symbols happens on the first call from the application. */ - /* - * XXX - should we call _pam_init_handlers() here ? The following - * is new as of Linux-PAM 0.55 - */ - if ( _pam_init_handlers(*pamh) != PAM_SUCCESS ) { _pam_system_log(LOG_ERR, "pam_start: failed to initialize handlers"); _pam_drop_env(*pamh); /* purge the environment */ -- cgit v1.2.3