similar to: dtsession PAM error

I'm trying to configure my Solaris 9 pam.conf for CDE login/password expiration using ADS security on W2003. If my AD account password is in good standing, my config works great in /etc/pam.conf. However - I'm having trouble getting it to recognize that my password in AD has expired to ask me to reset it on the CDE screen. With the config below - it just tells me "login

>> passdb { >> driver = pam >> } >> passdb { >> driver = pam >> name = pam >> } > Are those two passdb blocks intentional? > > One of them is missing the name parameter. doh. first removed. Aug 3 06:49:23 psg auth: in openpam_parse_chain(): /etc/pam.d/dovecot(1): missing or invalid facility Aug 3 06:49:23 psg dovecot:

While configuring my server with dovecot I noticed that the PAM authentication driver does not support the username_format option as does the password file driver. This didn't seem too hard to implement so I through together a patch. As you can see in the attached patch I only modify the username sent to PAM. Despit doing this I run into the domain lost

I'm having trouble getting dovecot to compile with PAM support. Output from the configure command says its checking for pam_start in -lpam .... no. I've checked, there is a pam_start in there. So how can I force configure to see what its looking for? I've tried the --with-pam switch and that doesn't work. I'm trying to build the latest RC7 on a Debian Sarge box. Regards

# dovecot --version 2.2.31 (65cde28) on freebsd 64 10.3 system converted to dovecot 2 against my will and consuming a lot of time sorting it out. i am glad google does not charge. have spent two hours on this one alone; and undoubtedly it is my st00pidity. so excuse my desperate posting to lazynet. cram-md5 works, pam not so much Aug 3 06:06:35 psg auth: in openpam_parse_chain():

Hi there, Other auth modules (eg passwd-file) allow a username_format to be specified, but not the PAM module. The use-case, is where I want a static userdb configuration which takes the domain into account but still want to use PAM for authentication, eg: userdb { driver = static args = uid=8 gid=12 home=/mnt/storage/mail/vhosts/%d/%n } passdb { driver = pam args = username_format=%n

Hi, I'm new here in the list so Hello to everyone! I'm compiling dovecot 1.0.10 with pam support in SLES 9 but i'm getting errors in config.log and it won't compile with pam support. Here are the results: s1:~/dovecot-1.0.10# ./configure --with-pam | grep pam checking for pam_start in -lpam... no and in config.log: configure:28830: checking for pam_start in -lpam

Just setup a new server on the weekend with Ubuntu 8.10 beta, and Dovecot 1.1.4. Every now and then, the IMAP server dies, and won't let users authenticate. It happens about once or twice a day. In /var/log/mail.log, you can see dovecot complaining about critial errors: Oct 21 14:46:16 tachikoma dovecot: imap-login: Login: user=<jason>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS

Fellow Dovecot'ers, I've -almost- got Dovecot completely functional, and I will add that it works just fine for non-authenticated POP3. The problem begins when I try to use authentication for same against the system's /etc/passwd section. This is the error message that comes up in /var/log/maillog Jul 9 21:14:10 featherweb dovecot: auth(default): pam(kyrrin at

When I add the --with-pam option in my configure command I get the following error: checking for pam_start in -lpam... no configure: error: Can't build with PAM support: libpam not found PAM is most certainly installed on the machine: ii libpam-modules 0.79-5 Pluggable Authentication Modules for PAM ii libpam-runtime 0.79-5 Runtime support

Hi, I was running the Ubuntu dovecot package until now, and decided to upgrade because of an issue with Thunderbird. I downloaded and compiled 1.0.8, and it's not starting up. The error I'm getting is: Dec 2 15:35:04 jfootoo dovecot: auth(default): Unknown passdb driver 'pam' (typo, or Dovecot was built without support for it? Check with dovecot --build-options) D I used

Hello there, I have winbind configured and working fine on a Solaris 8 machine pam is configured ok (I guess) as telnet/su'ing/smb access is working fine, OpenSSH 3.9 is configured with the following options: --prefix=/usr/local --sysconfdir=/etc/ssh --with-md5-passwords --with-default-path=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/ bin:/bin --with-ipv4-default

Hi, i'm quite new to dovecot. i built it from the stable-1.0 sources. i have the following error messages in syslog when trying to launch dovecot: dovecot: Dovecot v1.0-stable starting up dovecot: auth(default): Unknown passdb type 'pam' dovecot: Auth process died too early - shutting down dovecot: child 373 (auth) returned error 89 i googled a bit, and found some posts

This is actually something I had on my mind to write about in the past few -stable and alpha releases, but did not get to and instead always patched myself. Now having updated to the latest snapshot (which may be released as beta1), I stumbled on it again: In src/auth/passdb-pam.c, where the client host is passed to PAM, the code looks like this: #ifdef PAM_RHOST const char *host =

Hallo da mein English nicht so gut ist und bei der ?bersetzung auch noch Missverst?ndnisse auftretten k?nnten, hier das Orginal :-) Das Problem ist, dass bei der Kombination openssh pam und ldap, die Verbindung zum Ldapserver so lange offen gehalten wird bis die ssh Session geschlossen wird. Das ist nur bei SSH so ! Alle andere Dienste sprechen den Server an und schliessen nach Best?ttigung des

Hello ISSUE: Intermittently getting username and password authentication in clients both OUTLOOK 2007 and latest Thunderbird, indicating that the client is not authenticated with the server. Ie the username and password dialogue constantly reappears. This only appears as more users logged into the system. TEMP FIX: Restart Dovecot. LOG FILES Mail.err Jun 7 15:23:07 mail

http://bugzilla.mindrot.org/show_bug.cgi?id=117 ------- Additional Comments From djm at mindrot.org 2003-03-10 11:57 ------- Created an attachment (id=245) --> (http://bugzilla.mindrot.org/attachment.cgi?id=245&action=view) Use supplied username in pam_start calls always Make sshd always use supplied username (even if it is invalid) in calls to PAM ------- You are receiving this

Hi ya'll- I've got this odd openssh problem with Solaris 10 I was hoping someone could shed some light on. Not sure if it is a bug... Basically I'm trying to use pubkeys as an auth method, but am having issues. I can log in using passwords no problem, but as soon as it notices a matching public key it closes the connection. I ran the sshd server (on Solaris 10 box) in debug

Config: Solaris 8, OpenLDAP winbind backend, using AD for global users. Is there documentation on what service_name / module_type pairs are supported by pam_winbind? I've gone through the Samba-3 HOWTO book and internet searches, but haven't found anything difinitive. I have been able to tell through experimentation that winbind doesn't work with "rsh auth", giving a

When we installed OpenSSH 2.1.1p4 on our Solaris systems, our users noticed that it did not honor password expiration consistently with other Solaris login services. The patch below is against OpenSSH 2.2.0p1 and adds support for PAM password changes on expiration via pam_chauthtok(). A brief summary of changes: auth-pam.c: * change declaration of pamh to "static pam_handle_t *pamh",