search for: fetch_pam_environ

...R_IN_UTMPX) if (addr) { /* Added a brace here - Ged */ switch (addr->sa_family) { Solution for Makefile: Changed Makefile.in and added $(CFLAGS) to the compile lines for all the executables. Solution for sshd: HP-UX does not have a pam_getenvlist call. Changed the fetch_pam_environment function to return NULL if _HPUX_SOURCE was defined. /* Return list of PAM environment strings */ char **fetch_pam_environment(void) { #ifndef _HPUX_SOURCE /* HP-UX has not implemented this */ return(pam_getenvlist((pam_handle_t *)pamh)); #else return(NULL); #endif } Solution for...

Hi, the following patch changes the Cygwin specific function copy_environment() to not restricting the strlen of a single environment variable to 512 byte. The PAM specific function do_pam_environment() (also in session.c) has the same problem but I don't know if that's important for PAM since only PAM specific environment variables are copied in that function. The below patch fixes

...+ pam_retval = pam_set_item(pamh, PAM_TTY, "ssh"); if (pam_retval != PAM_SUCCESS) { fatal("PAM set tty failed: %.200s", - PAM_STRERROR((pam_handle_t *)pamh, pam_retval)); + PAM_STRERROR(pamh, pam_retval)); } #endif /* PAM_TTY_KLUDGE */ @@ -268,7 +320,7 @@ char **fetch_pam_environment(void) { #ifdef HAVE_PAM_GETENVLIST - return(pam_getenvlist((pam_handle_t *)pamh)); + return(pam_getenvlist(pamh)); #else /* HAVE_PAM_GETENVLIST */ return(NULL); #endif /* HAVE_PAM_GETENVLIST */ =================================================================== RCS file: RCS/auth-pam.h,v...

Here is a patch that does TIS auth via PAM. It's controlled by a switch in the sshd_config. You'd use it by having a PAM module that sets PAM_PROMPT_ECHO_ON. eg, you could use it with pam_skey or pam_smxs. The patch is against the 2.9.9p2 distribution. I'm not on the list, a reply if this patch is accepted would be great. (But not required, I know some folks have a distaste for

...:12:24 2001 +++ openssh-3.0.2p1/auth-pam.h Fri Feb 15 02:15:02 2002 @@ -7,7 +7,7 @@ void start_pam(const char *user); void finish_pam(void); -int auth_pam_password(struct passwd *pw, const char *password); +int auth_pam_password(struct passwd *pw, const char *password, int prompt_type); char **fetch_pam_environment(void); int do_pam_authenticate(int flags); int do_pam_account(char *username, char *remote_user); diff -uNr openssh-3.0.2p1.orig/auth1.c openssh-3.0.2p1/auth1.c --- openssh-3.0.2p1.orig/auth1.c Tue Nov 13 04:46:19 2001 +++ openssh-3.0.2p1/auth1.c Fri Feb 15 02:15:02 2002 @@ -85,7 +85,7 @@...

...38 2000 +++ openssh-2.1.1p4-hein/auth-pam.h Sun Aug 27 17:27:46 2000 @@ -5,7 +5,7 @@ void start_pam(struct passwd *pw); void finish_pam(void); -int auth_pam_password(struct passwd *pw, const char *password); +int auth_pam_password(struct passwd *pw, const char *password, int auth_type); char **fetch_pam_environment(void); int do_pam_account(char *username, char *remote_user); void do_pam_session(char *username, const char *ttyname); diff -urN -x *~ openssh-2.1.1p4/auth1.c openssh-2.1.1p4-hein/auth1.c --- openssh-2.1.1p4/auth1.c Sat Jul 8 02:44:14 2000 +++ openssh-2.1.1p4-hein/auth1.c Sun Aug 27 17:27:5...

As many of you know, OpenSSH 3.7.X, unlike previous versions, makes PAM authentication take place in a separate process or thread (launched from sshpam_init_ctx() in auth-pam.c). By default (if you don't define USE_POSIX_THREADS) the code "fork"s a separate process. Or if you define USE_POSIX_THREADS it will create a new thread (a second one, in addition to the primary thread). The