Re: About a bug in libpam-mysql package on squeeze
On Tue, 07 Feb 2012 23:50:23 +0200, Onur R. Bingol wrote:
> I am using these packages:
> root@debian:~# lsb_release -a
> Description: Debian GNU/Linux 6.0.4 (squeeze) Release: 6.0.4
> Codename: squeeze
> root@debian:~# dpkg --status libpam-mysql ...
> Version: 0.7~RC1-4+b1
> I have created a logging table with the following credentals:
> and my pam-mysql.conf file is
> log.enabled = 1
> log.table = pam_logs
> log.message_column = pam_logs.message
> #log.pid_column = pid
> log.user_column = pam_logs.username
> log.host_column = pam_logs.hostname
> #log.rhost_column = (logrhostcolumn) *2
> log.time_column = pam_logs.time
> Loading pam_mysql.so with "config_file=/etc/pam-mysql.conf" as written
> on the README file.
I think the "README.Debian" has a little error. It says the config file
is located at "/etc/libpam-mysql.conf" while the filename is indeed "pam-
> As you see log.pid_column is disabled. However, I am getting these logs
> in my /var/log/auth.log
> Feb 7 23:15:23 debian sshd: pam_mysql - INSERT INTO pam_logs (pam_logs.message, pam_logs.username, pam_logs.hostname, , pam_logs.time) VALUES ('AUTHENTICATION SUCCESS (FIRST_PASS)', 'deneme', '127.0.1.1', '3391', NOW())
(I'm keeping all in one line for better readability)
Yup. There's an empty field. And there's the data which contains. Weird.
> Feb 7 23:15:23 debian sshd: pam_mysql - MySQL error (You have an
> error in your SQL syntax; check the manual that corresponds to your
> MySQL server version for the right syntax to use near ' pam_logs.time)
> VALUES ('AUTHENTICATION SUCCESS (FIRST_PASS)', 'deneme', '127.0.' at
> line 1)
> Although pid column is disabled in pam-mysql.conf file, it makes a query
> including the pid value or somehow it needs it.
Mmm, your reasoning and findings look right to me, the commented field
(#) shoudn't be added to the database. But before anything, how about
increasing the log verbosity ("verbose 1")? Maybe it can give you more
> Does this information is enough for submitting a bug report on
> libpam-mysql package?
I'd say yes. Even though the upstream package seems to be quite old (last
update on 2006? :-?).