First off, I think this bug came about after this change mentioned in
"2005-09-23 Moriyoshi Koizumi <email@example.com>
* pam_mysql.c: (pam_mysql_parse_args): change option parsing
behaviour so "=" following each option name is not needed.
Problem is that if I have a long WHERE clause, it gets chopped off at the
first space encountered.
where=domain='foo.net' AND status=1
Will be parsed as:
and "AND status=" parsed as a config file error.
In the README, there are examples that show long strings either
quoted or with brackets around them. Brackets don't seem to parse,
and if I quote everything like this:
where="domain='foo.net' AND status=1"
The parser reads the where clause as:
It includes the first quote literally and still truncates the where clause
at the first space it encounters.