Re: Fwd: Bug#249083: postgresql: Postgres SIGSEGV if wins in nsswitch.conf

Hi again!

On 2004-05-25 15:13 -0400, Tom Lane wrote:
> I said:
> > I would suggest adding more paranoia along these lines:
>=20
> Actually the correct patch is as per attached.  Even without a core
> dump, the original code would not print the token that was really
> causing the problem :-(.  Please apply this patch and then tell us
> what you see with winbind.

The submitter of this bug eventually reported back (there was a
problem with his email address) and tested the updated package (with
your patch); unfortunately it seems that the patch did not improve the
output very much :-( He wrote:

----------------------------------------------------
Started by /etc/init.d/postgresql:

2004-06-07 14:24:59 [6455] LOG:  authentication file token too long, skippi=
ng: "(garbage)"

I piped the garbage through xxd and got:
986e 0241 9131 f840

I ran it again from the command line, as user postgres and got, instead:
98e3 ed40 9101 e340

These garbage strings are repeatable.

In either case, I did get the seg fault.
----------------------------------------------------

Does that say anything to anybody?

Thanks and have a nice day!

Martin

--=20
Martin Pitt                 Debian GNU/Linux Developer
martin@piware.de                      mpitt@debian.org
http://www.piware.de             http://www.debian.org