From: | "Douglas, Ryan" <RDouglas(at)arbinet(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Magnus Hagander" <magnus(at)hagander(dot)net>, "pgsql-bugs" <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #5121: Segmentation Fault when using pam w/ krb5 |
Date: | 2009-10-16 20:38:36 |
Message-ID: | 706C25916A1ADD489F69906EC24FC07E026FE085@vamail02.TheXchange.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
It works like champ... cool.. thanks.
-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Friday, October 16, 2009 4:15 PM
To: Douglas, Ryan
Cc: Magnus Hagander; pgsql-bugs
Subject: Re: [BUGS] BUG #5121: Segmentation Fault when using pam w/ krb5
"Douglas, Ryan" <RDouglas(at)arbinet(dot)com> writes:
> You were right. According to the trace msg[0] is null.
Hah. This must be triggered by something Active Directory does that a
KDC doesn't, because I'm still not seeing it here. But anyway the
problem is clear now, we have to avoid referencing msg[0] when num_msg
is zero.
Please try the attached patch and see if it behaves sanely for you.
This is based on openssh's PAM callback, so it ought to be more robust
than what we had. (This is against 8.4 branch tip, but it should apply
to 8.4.1 with maybe a few lines' offset.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2009-10-16 21:13:16 | Re: BUG #5123: bug in window function "last_value" |
Previous Message | Tom Lane | 2009-10-16 20:15:22 | Re: BUG #5121: Segmentation Fault when using pam w/ krb5 |