aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorxujing <xujing125@huawei.com>2024-12-03 20:11:18 +0800
committerDmitry V. Levin <ldv@strace.io>2024-12-03 12:31:16 +0000
commita2fb0dd306db943e4165f530534b01d00298065f (patch)
tree34c35d6688f3145fd2ee624167b55fef03175e2a
parent9b5182d4781bcd6fb37a4030faf325965fde3e93 (diff)
downloadpam-a2fb0dd306db943e4165f530534b01d00298065f.tar.gz
pam-a2fb0dd306db943e4165f530534b01d00298065f.tar.bz2
pam-a2fb0dd306db943e4165f530534b01d00298065f.zip
pam_unix: fix diagnostic message in debug mode
When configured using -Dpam-debug=true, _pam_unix_approve_pass prints a diagnostic message with addresses of password strings. Apparently, since the times predating the git history of the project in this diagnostic message the addresses of the old and new passwords were mixed up.
-rw-r--r--modules/pam_unix/pam_unix_passwd.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/modules/pam_unix/pam_unix_passwd.c b/modules/pam_unix/pam_unix_passwd.c
index 4a3784a5..fc19d474 100644
--- a/modules/pam_unix/pam_unix_passwd.c
+++ b/modules/pam_unix/pam_unix_passwd.c
@@ -545,7 +545,7 @@ static int _pam_unix_approve_pass(pam_handle_t * pamh
const char *remark = NULL;
int retval = PAM_SUCCESS;
- D(("&new=%p, &old=%p", pass_old, pass_new));
+ D(("&new=%p, &old=%p", pass_new, pass_old));
D(("new=[%s]", pass_new));
D(("old=[%s]", pass_old));