On Wed, 22 Jul 2009, Timo Sirainen wrote:
I'm not really sure why you think that's wrong. The code is there
exactly for the reason that if PAM changes username Dovecot will notice
it and starts using it.
Actually, that makes a lot of sense. I was confusing other (proximate)
logs with the impl
On Wed, 2009-07-22 at 14:04 -0400, Aaron Richton wrote:
> In 1.2.1 there's:
>
> passdb-pam.c:230 status = pam_get_item(pamh, PAM_USER, &item);
> passdb-pam.c:237 auth_request_set_field(request, "user", item, NULL);
>
> so "item" is PAM_USER, which is then checked by auth_request_s
In 1.2.1 there's:
passdb-pam.c:230 status = pam_get_item(pamh, PAM_USER, &item);
passdb-pam.c:237 auth_request_set_field(request, "user", item, NULL);
so "item" is PAM_USER, which is then checked by auth_request_set_field:
1022 if (strcmp(request->user, value) !=
