search for: mm_do_pam_account

...like: === other account required pam_ldap.so.1 === in pam.conf no logins are possible. Below is the pertaining section of the sshd run output with -ddd option: === debug3: monitor_read: checking request 52 debug3: mm_answer_pam_free_ctx debug3: mm_request_send entering: type 53 debug3: mm_do_pam_account entering debug3: mm_request_send entering: type 44 debug3: mm_request_receive_expect entering: type 45 debug3: mm_request_receive entering debug2: monitor_read: 52 used once, disabling now debug3: mm_request_receive_expect entering: type 44 debug3: mm_request_receive entering debug3: do_pam_account...

...: waiting for MONITOR_ANS_PAM_FREE_CTX debug3: monitor_read: checking request 52 debug3: mm_answer_pam_free_ctx debug3: mm_request_receive_expect entering: type 53 debug3: mm_request_receive entering debug3: mm_request_send entering: type 53 debug2: monitor_read: 52 used once, disabling now debug3: mm_do_pam_account entering debug3: mm_request_receive_expect entering: type 44 debug3: mm_request_receive entering debug3: mm_request_send entering: type 44 debug3: mm_request_receive_expect entering: type 45 debug3: mm_request_receive entering debug1: Calling cleanup 0x4af30(0x0) Bus Error I trussed the process a...

...4252 style communication. Then later. debug2: ## DH: userauth_finish [preauth] debug3: auth2_update_methods_lists: updating methods list after "password" [preauth] debug2: authentication methods list 0 complete [preauth] debug2: ## DH: about to do_pam_account [preauth] debug3: mm_do_pam_account entering [preauth] debug3: mm_request_send entering: type 102 [preauth] debug3: mm_request_receive_expect entering: type 103 [preauth] debug3: mm_request_receive entering [preauth] debug3: mm_do_pam_account returning 1 [preauth] debug2: ## DH: done do_pam_account - no message [preauth] debug3...

On Sun, Mar 01, 2015 at 03:23:04AM +1100, Damien Miller wrote: > > > On Sat, 28 Feb 2015, The Doctor wrote: > > > BSD/OS issues > > > > with 1.0.2a dev > > Thanks for testing. > You are welcome. > > make tests > > > > regress/netcat.c:656: `on' undeclared (first use in this function) > > regress/netcat.c:656: (Each

Hi, There seems to be no way for PAM to inform a user why her ssh login attempt is being denied. Niether PAM_TEXT_INFO or PAM_ERROR_MSG conversation messages are passed on to the user by sshd unless the login is successful. This is causing great frustration for us at several sites where users can't figure out why their logins aren't working. Would a patch be accepted to display such

...debug2: monitor_read: 54 used once, disabling now debug3: mm_request_receive_expect entering: type 46 debug3: mm_request_receive entering debug3: mm_sshpam_free_ctx: waiting for MONITOR_ANS_PAM_FREE_CTX debug3: mm_request_receive_expect entering: type 55 debug3: mm_request_receive entering debug3: mm_do_pam_account entering debug3: mm_request_send entering: type 46 debug1: do_pam_account: called debug3: mm_request_send entering: type 47 Accepted keyboard-interactive/pam for emillbrandt from 192.168.1.42 port 4825 ssh2 debug1: monitor_child_preauth: emillbrandt has been authenticated by privileged process de...

https://bugzilla.mindrot.org/show_bug.cgi?id=983 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|pgsery at swcp.com |djm at mindrot.org --- Comment #58 from Damien Miller

...receive entering debug3: mm_request_receive entering debug3: monitor_read: checking request 22 debug1: ssh_rsa_verify: signature correct debug3: mm_answer_keyverify: key 99468 signature verified debug3: mm_request_send entering: type 23 debug2: userauth_pubkey: authenticated 1 pkalg ssh-rsa debug3: mm_do_pam_account entering debug3: mm_request_send entering: type 48 debug3: mm_request_receive_expect entering: type 49 debug3: mm_request_receive entering debug3: mm_request_receive_expect entering: type 48 debug3: mm_request_receive entering debug1: do_pam_account: called debug3: PAM: do_pam_account pam_acct_mgmt...

...type 11 debug3: mm_request_receive_expect entering: type 46 debug3: mm_request_receive entering debug3: mm_auth_password: waiting for MONITOR_ANS_AUTHPASSWORD debug3: mm_request_receive_expect entering: type 11 debug3: mm_request_receive entering debug3: mm_auth_password: user authenticated debug3: mm_do_pam_account entering debug3: mm_request_send entering: type 46 debug1: do_pam_account: called debug3: PAM: do_pam_account pam_acct_mgmt = 0 (Success) debug3: mm_request_send entering: type 47 Accepted password for root from 15.1.196.211 port 1023 ssh2 debug1: monitor_child_preauth: root has been authenticated...

...ing debug3: monitor_read: checking request 11 debug3: PAM: sshpam_passwd_conv called with 1 messages debug1: PAM: password authentication accepted for yost debug3: mm_answer_authpassword: sending result 1 debug3: mm_request_send entering: type 12 debug3: mm_auth_password: user authenticated debug3: mm_do_pam_account entering debug3: mm_request_send entering: type 47 debug3: mm_request_receive_expect entering: type 48 debug3: mm_request_receive entering debug3: mm_request_receive_expect entering: type 47 debug3: mm_request_receive entering debug1: do_pam_account: called debug3: PAM: do_pam_account pam_acct_mgmt...

...monitor_read: checking request 23 debug1: ssh_dss_verify: signature correct debug3: mm_answer_keyverify: key 0x7f8a5c7b9e40 signature verified debug3: mm_request_send entering: type 24 debug3: mm_request_receive_expect entering: type 47 debug2: userauth_pubkey: authenticated 1 pkalg ssh-dss debug3: mm_do_pam_account entering debug3: mm_request_send entering: type 47 debug3: mm_request_receive_expect entering: type 48 debug3: mm_request_receive entering debug3: mm_request_receive entering debug1: do_pam_account: called debug3: PAM: do_pam_account pam_acct_mgmt = 0 (Success) debug3: mm_request_send entering: typ...

On 30/06/2023 09:56, Damien Miller wrote: > It's very hard to figure out what is happening here without a debug log. > > You can get one by stopping the listening sshd and running it manually > in debug mode, e.g. "/usr/sbin/sshd -ddd" Or starting one in debug mode on a different port, e.g. "-p99 -ddd"

...d[8569]: debug3: mm_get_keystate: Getting Network I/O buffers Dec 16 22:22:13 knasim-ubuntu1 sshd[8569]: debug3: mm_auth_password: user authenticated [preauth] Dec 16 22:22:13 knasim-ubuntu1 sshd[8569]: debug3: mm_request_receive entering [preauth] Dec 16 22:22:13 knasim-ubuntu1 sshd[8569]: debug3: mm_do_pam_account returning 1 [preauth] Dec 16 22:22:13 knasim-ubuntu1 sshd[8569]: debug3: mm_send_keystate: Sending new keys: 0x7f17549728f0 0x7f17549733a0 [preauth] Dec 16 22:22:13 knasim-ubuntu1 sshd[8569]: debug3: mm_newkeys_to_blob: converting 0x7f17549728f0 [preauth] Dec 16 22:22:13 knasim-ubuntu1 sshd[8569]:...

Hi folks, I came across this issue on both stock CentOS(v6.4) and Ubuntu(14.04 LTS) and was wondering if any of you have seen it. As far as I can tell this seems like a day-1 bug to me. PROBLEM: If I expire a linux user's password (passwd -e <user>) and then log in via ssh, it will prompt you for a password change. On changing the password successfully, sshd will drop the connection