search for: pam_get_data

https://bugzilla.mindrot.org/show_bug.cgi?id=2548 Bug ID: 2548 Summary: Make pam_set_data/pam_get_data work with OpenSSH Product: Portable OpenSSH Version: 7.2p1 Hardware: Sparc OS: Solaris Status: NEW Severity: major Priority: P5 Component: PAM support Assignee: unassigned-bugs at mindrot.org...

Let me refine my previous question: > Can anyone provide some insight into why the auth-pam module uses a fork in > pthread_create (auth-pam.c)? This completely breaks the ability of one PAM function > to pass data to others via the pam_set_data/pam_get_data functions. Can anyone tell me how to #define USE_POSIX_THREADS when building --with-pam defined? The autoconfig stuff doesn't test for pthreads libraries, so by default you get threads simulated by Unix processes. Presumably there ought to be an "official" way to specify this....

Hello list, Bug 688 is causing me a massive headache on OS X. The fact that each PAM authentication takes place in a separate process means the PAM context data isn't shared and therefore prevents the passing of data between modules. (pam_set_data, and pam_get_data) Compiling with pthreads isn't really an option because of the added security risk and the fact that some of the PAM modules are not thread safe and would be troublesome to make thread safe. Storing the data in the environment really isn't an option, as it is sensitive. Is there anoth...

Hello, I've developed a custom PAM module which only allows a user to authenticate to the server only if another user of the same machine also authenticates succesfully. It's currently a simple module which also works as a PAM aware application since it authenticates each user with PAM itself. Both the pamtester utility and su can use this module correctly. However, when I try to use

...int" nsswitch/pam_winbind.c:546: error: syntax error before "int" nsswitch/pam_winbind.c: In function `pam_sm_acct_mgmt': nsswitch/pam_winbind.c:558: warning: passing arg 2 of `pam_get_user' from incompatible pointer type nsswitch/pam_winbind.c:580: warning: passing arg 3 of `pam_get_data' from incompatible pointer type nsswitch/pam_winbind.c: At top level: nsswitch/pam_winbind.c:614: error: syntax error before "int" nsswitch/pam_winbind.c:624: error: syntax error before "int" nsswitch/pam_winbind.c:636: error: syntax error before "int" nsswitch/pam...

...king whether to use AFS... no checking whether to use DCE/DFS auth... no checking whether to use Kerberos IV... no checking whether to use Kerberos 5... no checking whether to use AUTOMOUNT... no checking whether to use SMBMOUNT... no checking whether to use PAM password database... no checking for pam_get_data in -lpam... no checking whether to use pam_smbpass... no checking for crypt... yes checking for a crypt that needs truncated salt... yes checking whether to use TDB SAM database... no checking whether to use LDAP SAM database... no checking whether to use NISPLUS SAM database... no checking whether...

...configure:11844: checking whether to use Kerberos IV configure:11919: checking whether to use Kerberos 5 configure:11947: checking whether to use AUTOMOUNT configure:11972: checking whether to use SMBMOUNT configure:12009: checking whether to use PAM password database configure:12035: checking for pam_get_data in -lpam configure:12081: checking whether to use pam_smbpass configure:12282: checking whether to use TDB SAM database configure:12308: checking whether to use LDAP SAM database configure:12479: checking whether to use NISPLUS SAM database configure:12507: checking whether to use traditional smbpa...

...king whether to use AFS... no checking whether to use DCE/DFS auth... no checking whether to use Kerberos IV... no checking whether to use Kerberos 5... no checking whether to use AUTOMOUNT... no checking whether to use SMBMOUNT... no checking whether to use PAM password database... no checking for pam_get_data in -lpam... no checking whether to use pam_smbpass... no checking for crypt... yes checking for a crypt that needs truncated salt... no checking whether to use TDB SAM database... no checking whether to use LDAP SAM database... no checking whether to use NISPLUS SAM database... no checking whether...

Hello, I am running HP-UX 11 with Samba 2.2.5 binaries for HPUX and I keep getting the error that Samba can't find the unicode_map.xxx file. Well, I notice that all I have in /usr/local/samba/lib/codepages is codepage type files, not unicode. Why do the binaries not include a compiled make_unicodemap? I did download the source and found the .c file for the command. When I try to run

...king whether to use AFS... no checking whether to use DCE/DFS auth... no checking whether to use Kerberos IV... no checking whether to use Kerberos 5... no checking whether to use AUTOMOUNT... no checking whether to use SMBMOUNT... no checking whether to use PAM password database... no checking for pam_get_data in -lpam... (cached) no checking whether to use pam_smbpass... no checking for crypt... (cached) yes checking for a crypt that needs truncated salt... (cached) yes checking whether to use TDB SAM database... no checking whether to use LDAP SAM database... no checking whether to use NISPLUS SAM data...

...is function) pam_ldap.c:2668: error: `PAM_SERVICE_ERR' undeclared (first use in this function) pam_ldap.c: At top level: pam_ldap.c:2739: error: syntax error before '*' token pam_ldap.c: In function `_pam_ldap_get_session': pam_ldap.c:2746: warning: implicit declaration of function `pam_get_data' pam_ldap.c:2746: error: `pamh' undeclared (first use in this function) pam_ldap.c:2746: warning: dereferencing type-punned pointer will break strict-aliasing rules pam_ldap.c:2746: error: `PAM_SUCCESS' undeclared (first use in this function) pam_ldap.c:2756: error: `username' undec...

...ing whether to use AFS... no checking whether to use DCE/DFS auth... no checking whether to use Kerberos IV... no checking whether to use Kerberos 5... no checking whether to use AUTOMOUNT... no checking whether to use SMBMOUNT... no checking whether to use PAM password database... yes checking for pam_get_data in -lpam... (cached) no checking whether to use pam_smbpass... no checking whether to use TDB SAM database... no checking whether to use LDAP SAM database... no checking whether to use NISPLUS SAM database... no checking whether to use traditional smbpasswd file... yes checking whether to use NISPL...

...yes checking for memory keytab support... no checking whether Active Directory and krb5 support is used... yes checking whether to build experimental passdb libraries... no checking whether to use automount... no checking whether to use smbmount... no checking whether to use PAM... no checking for pam_get_data in -lpam... yes checking whether to use pam_smbpass... no checking for library containing crypt... -lcrypt checking for a crypt that needs truncated salt... no checking whether to use LDAP SAM 2.2 compatible configuration... no checking whether to use NISPLUS_HOME... no checking whether to use sysl...

...king whether to use AFS... no checking whether to use DCE/DFS auth... no checking whether to use Kerberos IV... no checking whether to use Kerberos 5... no checking whether to use AUTOMOUNT... no checking whether to use SMBMOUNT... no checking whether to use PAM password database... no checking for pam_get_data in -lpam... no checking whether to use pam_smbpass... no checking for crypt... yes checking for a crypt that needs truncated salt... yes checking whether to use TDB SAM database... no checking whether to use LDAP SAM database... no checking whether to use NISPLUS SAM database... no checking whether...

...or Active Directory and krb5 support... auto configure: WARNING: Active Directory Support requires LDAP support checking whether to build experimental passdb libraries... no checking whether to use automount... no checking whether to use smbmount... no checking whether to use PAM... no checking for pam_get_data in -lpam... no checking whether to use pam_smbpass... no checking for library containing crypt... -lcrypt checking for a crypt that needs truncated salt... no checking whether to use LDAP SAM 2.2 compatible configuration... no checking whether to use NISPLUS_HOME... no checking whether to use syslo...

...king whether to use AFS... no checking whether to use DCE/DFS auth... no checking whether to use Kerberos IV... no checking whether to use Kerberos 5... no checking whether to use AUTOMOUNT... no checking whether to use SMBMOUNT... no checking whether to use PAM password database... no checking for pam_get_data in -lpam... (cached) yes checking whether to use pam_smbpass... no checking for crypt... (cached) yes checking for a crypt that needs truncated salt... (cached) no checking whether to use TDB SAM database... no checking whether to use LDAP SAM database... no checking whether to use NISPLUS SAM data...

...cking for keyblock in krb5_keytab_entry... no checking whether Active Directory and krb5 support is used... yes checking whether to build experimental passdb libraries... no checking whether to use automount... no checking whether to use smbmount... no checking whether to use PAM... no checking for pam_get_data in -lpam... yes checking whether to use pam_smbpass... no checking for library containing crypt... none required checking for a crypt that needs truncated salt... no checking whether to use LDAP SAM 2.2 compatible configuration... yes checking whether to use NISPLUS_HOME... no checking whether to u...

...cking for keyblock in krb5_keytab_entry... no checking whether Active Directory and krb5 support is used... yes checking whether to build experimental passdb libraries... no checking whether to use automount... no checking whether to use smbmount... no checking whether to use PAM... no checking for pam_get_data in -lpam... yes checking whether to use pam_smbpass... no checking for library containing crypt... none required checking for a crypt that needs truncated salt... no checking whether to use LDAP SAM 2.2 compatible configuration... yes checking whether to use NISPLUS_HOME... no checking whether to u...

...hecking whether to try PAM support... auto checking security/pam_appl.h usability... yes checking security/pam_appl.h presence... yes checking for security/pam_appl.h... yes checking pam/pam_appl.h usability... no checking pam/pam_appl.h presence... no checking for pam/pam_appl.h... no checking for pam_get_data in -lpam... yes checking for security/pam_modules.h... yes checking for pam/pam_modules.h... no checking security/pam_ext.h usability... no checking security/pam_ext.h presence... no checking for security/pam_ext.h... no checking security/_pam_macros.h usability... no checking security/_pam_macros....

...: not found Checking for avahi_strerror : not found Checking for macro avahi_strerror : not found Checking for header pam/pam_appl.h : no Checking for pam_get_data : ok Checking for header security/pam_ext.h : yes Checking for header security/_pam_macros.h : yes Checking for header pam/pam_ext.h...