Re: [Pam-mysql-general] SELECT returned no result

[Moriyoshi K. <mor...@at...>]

xyon wrote:
> Figured I'd chime in and let everyone know of my progress.
> 
> I used Moriyoshi's patch for custom queries in pam_mysql (linked below).
> Even though I still cannot match against the Scalix %u (username) value,
> I can match on the %p (password) value, so things are at least moving in
> the proper direction.

For the proper record, that's not mine. I'm just a project member who
handled the patch entry.

> I've tried everything with the "%u" value (TRIM, LOWER, etc), and yet it
> still refuses to match when coming from Scalix. So this problem all
> along wasn't a pam_mysql thing, but a Scalix thing. Although this has
> been a great learning experience for me, I apologize if I've caused any
> undue frustration.

No problem. Did you try strace and see anything suspicious among the
calls? The query should've appeared as following:

send(3, "<83>Apr  7 16:28:00 pamtester: pam_mysql - SELECT pwd FROM
users WHERE scalix = \'Test User\'", 91, MSG_NOSIGNAL) = 91
poll([{fd=4, events=POLLIN|POLLPRI}], 1, 0) = 0
write(4, "1\0\0\0\3SELECT pwd FROM users WHERE scalix = \'Test User\'",
53) = 53
read(4,
"\1\0\0\1\1*\0\0\2\3def\4test\5users\5users\3pwd\3pwd\f\10\0\377\0\0\0\375\1\20\0\0\0\5\0\0\3\376\0\0\2\0\5\0\0\4\4test\5\0\0\5\376\0\0\2\0",
16384) = 78

-- 
Moriyoshi Koizumi <mor...@at...>