Skip site navigation (1) Skip section navigation (2)

Re: BUG #5121: Segmentation Fault when using pam w/ krb5

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Douglas, Ryan" <RDouglas(at)arbinet(dot)com>
Cc: pgsql-bugs(at)postgreSQL(dot)org
Subject: Re: BUG #5121: Segmentation Fault when using pam w/ krb5
Date: 2009-10-16 15:11:00
Message-ID: 6590.1255705860@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Well, we certainly are not going to break pq_recvbuf in such a
fundamental way as that ;-).  I think that the more likely place
to work around this is going to be in pam_passwd_conv_proc() in
src/backend/libpq/auth.c.  In particular, I see that when it gets
a NULL from recv_password_packet (which is what's going to happen
when pq_recvbuf returns EOF), it returns PAM_CONV_ERR without
bothering to set *resp.  I wonder whether we need to be initializing
*resp to NULL, or even making it really valid?

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2009-10-16 15:24:58
Subject: Re: BUG #5118: start-status-insert-fatal
Previous:From: Kevin GrittnerDate: 2009-10-16 15:08:12
Subject: Re: BUG #5118: start-status-insert-fatal

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group