search for: pam_lastlog

Hi, this was originally reported on ports@. [1] Someone noticed that after after running sudo their session disappeared when running `w` afterwards. I've done a little experimenting and this is caused when pam_lastlog.so is included in sudo's pam file. This results in the user still being logged in though according to the system logs the user has logged out. Here's an example: [tom@releng-7-fbsd tom]$ w 12:50AM up 6 days, 12:30, 2 users, load averages: 0.24, 0.31, 0.30 USER TTY FROM...

https://bugzilla.mindrot.org/show_bug.cgi?id=2049 Priority: P5 Bug ID: 2049 Assignee: unassigned-bugs at mindrot.org Summary: Request for a configurable option for SFTP to display login information to the user after a successful login. Severity: enhancement Classification: Unclassified

...on, do_pam_conversation(), that fed text to the client. In OpenSSH 3.7.1p2, this is no longer the case: session modules run with a conversation function that just returns PAM_CONV_ERR. This means that simple session modules whose job involves printing text on the user's terminal no longer work: pam_lastlog, pam_mail, and pam_motd. Can somebody explain to me why this change was made (as part of the FreeBSD PAM merge, apparently), or if it was a mistake? I realize that session modules are now run as root, but I'd have thought that modules should be trusted code and don't need to have their out...

...9;SSH should support XYZ feature.' unless it's directly related to portability.) Or if there is anything on this list that has been completed. (Namely Tru64 SIA support?) Thanks. -Ben Programming: - Replacement for setproctitle() - HP/UX support only currently - Improve PAM support (a pam_lastlog module will cause sshd to exit) - Complete Tru64 SIA support Documentation: - More and better - Install FAQ? - General FAQ on S/Key, TIS, RSA, RSA2, DSA, etc and suggestions on when it would be best to use them. - Create a Documentation/ directory? Clean up configure/makefiles: - Clean up con...

...th sufficient pam_winbind.so debug auth required pam_unix.so use_first_pass shadow auth required pam_env.so # [1] account sufficient pam_winbind.so debug account required pam_unix.so use_first_pass session required pam_unix.so session optional pam_lastlog.so # [1] session optional pam_motd.so # [1] session optional pam_mail.so standard noenv # [1] session required pam_limits.so password required pam_unix.so joined the domain and started smbd, nmbd and winbindd. When I execute wbinfo -u I get 0xc0000022. I googled around...

...rst_pass nullok # account account required pam_winbind.so #account required pam_krb5.so account required pam_login_access.so account required pam_unix.so # session #session optional pam_ssh.so session required pam_lastlog.so no_fail # password password sufficient pam_winbind.so try_first_pass #password sufficient pam_krb5.so no_warn try_first_pass password required pam_unix.so no_warn try_first_pass thanks for every help or hint you c...

...ck.so service=system-auth #session required pam_stack.so service=system-auth #session optional pam_console.so session required /lib/security/pam_mkhomedir.so skel=/etc/skel/ umask=0022 password required pam_unix.so nullok obscure min=4 max=8 session required pam_unix.so session optional pam_lastlog.so session optional pam_motd.so session optional pam_mail.so standard noenv I have tried many varations of this file from various postings but all to no avail the relevant part of smb.conf follow # Global parameters [global] workgroup = LEARNINGDOMAIN realm = LEARNINGDOMAIN.ORG...

...arn try_first_pass auth required pam_unix.so no_warn try_first_pass nullok # account #account required pam_krb5.so account required pam_login_access.so account required pam_unix.so # session #session optional pam_ssh.so session required pam_lastlog.so no_fail session required /usr/local/lib/pam_mkhomedir.so skel=/usr/local/etc/skel # password #password sufficient pam_krb5.so no_warn try_first_pass password required pam_unix.so no_warn try_first_pass

...d pam_unix.so use_first_pass shadow auth required pam_env.so # [1] account sufficient pam_winbind.so account required pam_unix.so use_first_pass session sufficient pam_mkhomedir.so skel=/etc/skel umask=0022 session required pam_unix.so session optional pam_lastlog.so # [1] session optional pam_motd.so # [1] session optional pam_mail.so standard noenv # [1] session required pam_limits.so password required pam_unix.so What am I missing here or doing wrong? Not sure if any other settings are relevant, and hate blasting the list wit...

Hi, I just ltraced ssh to see why it prints the lastlog twice instead of one time. I think the bug seems to be in the parsing of the lastlog-entry and I especially think that the function lastlog_populate_entry is the buggy one, but I'm not sure, as I'm not very familar with the code. So if someone of you, would please trace this bug down and fix it, I would really appreciate that.

...want to mention the following problem: Not only changing expired passwords when privilege separation is enabled in combination with PAM is not working (although the current patches seem to solve this one). Also some PAM session modules do not work the way they are supposed to. For instance, the pam_lastlog module. This module gets and updates the last successful login attempt for a specific user in /var/log/lastlog. When privilege separation mode is enabled, not enough privileges are available to read and update lastlog (root:root 0640). Changing the permissions to 0666 (obviously not something y...

.../etc/pam.d/login: auth required pam_securetty.so auth required pam_nologin.so auth sufficient pam_winbind.so debut auth requires pam_env.so auth required pam_unix.so use_first_pass account sufficient pam_winbind.so debug account required pam_unix.so session required pam_unix.so session optional pam_lastlog.so password required pam_unix.so nullok when i give a look at winbind's log, it seems to be good : "plaintext autehtication for user SCIENCEU+pitie return NT_STATUS_OK (PAM 0) " what's going wrong ? please helllp ...! thanks a lot! ---------------------------------...

...red pam_env.so debug auth sufficient pam_winbind.so debug auth required pam_unix.so use_first_pass nullok debug account required pam_winbind.so debug session required pam_mkhomedir.so skel=/etc/skel/ umask=002 session required pam_unix.so debug session optional pam_lastlog.so session optional pam_motd.so session optional pam_mail.so standard noenv password required pam_unix.so nullok obscure min=4 max=8 md5 ... but I doubt these are of any importance, since when I start winbindd -d 4 -i I get: added interface ip=192.168.6.102 bcast=192.168.6.255 nmask...

...required pam_listfile.so item=user sense=allow file=/etc/loginusers onerr=fail auth required pam_nologin.so auth required pam_unix.so auth required pam_env.so # [1] account required pam_unix.so session required pam_unix.so session optional pam_lastlog.so # [1] session optional pam_motd.so # [1] session optional pam_mail.so standard noenv # [1] session required pam_limits.so password required pam_unix.so --- -- Sakari Ailus sakari.ailus at luukku.com

...# account account required /usr/lib/pam_winbind.so #account required pam_krb5.so account required pam_login_access.so account required pam_unix.so # session #session optional pam_ssh.so session required pam_lastlog.so no_fail # password password sufficient /usr/lib/pam_winbind.so try_first_pass #password sufficient pam_krb5.so no_warn try_first_pass password required pam_unix.so no_warn try_first_pass ****************************copy end**...

...red pam_shells.so auth required pam_nologin.so auth include system-auth account required pam_access.so account required pam_nologin.so account include system-auth account required pam_tally.so onerr=succeed password include system-auth session required pam_env.so session optional pam_lastlog.so session include system-auth session optional pam_ck_connector.so nox11 session optional pam_motd.so motd=/etc/motd session optional pam_mail.so file /etc/pam.d/system-auth /etc/pam.d/system-auth: symbolic link to `system-auth-winbind' cat /etc/pam.d/system-auth-winbind #%PAM-1.0 # $H...

...# Standard Un*x authentication. The "nullok" line allows passwordless # accounts. auth required pam_unix.so nullok likeauth try_first_pass account required pam_unix.so session required pam_unix.so session optional pam_lastlog.so session optional pam_motd.so session optional pam_mail.so standard noenv password required /lib/security/pam_cracklib.so retry=3 password sufficient /lib/security/pam_unix.so nullok use_authtok shadow md5 password required /lib/security/pam_deny.so

Hello Community, is there someone who has winbind working on SUSE 8.X? On my system the authenication of the domain users simply does not work getent passwd shows all domain users gentent group shows all domain groups Login as domain user: Login incorrect! There seems to be no pam_stack.so on SUSE. Can it work without it? How can I fix ist? How can I trace the cause of the disfunction? I would

...auth requisite pam_securetty.so auth requisite pam_nologin.so session required pam_selinux.so close session required pam_env.so readenv=1 session required pam_env.so readenv=1 envfile=/etc/default/locale @include common-auth auth optional pam_group.so session required pam_limits.so session optional pam_lastlog.so session optional pam_motd.so session optional pam_mail.so standard @include common-account @include common-session @include common-password session required pam_selinux.so open # /etc/nsswitch.conf passwd: files ldap shadow: files ldap group: files ldap hosts: files mdns4_minimal [NOTFOUND=ret...

...# account account sufficient /usr/local/lib/pam_winbind.so #account required pam_krb5.so account required pam_login_access.so account required pam_unix.so # session #session optional pam_ssh.so session required pam_lastlog.so no_fail # password password sufficient /usr/local/lib/pam_winbind.so try_first_pass #password sufficient pam_krb5.so no_warn try_first_pass password required pam_unix.so no_warn try_first_pass