[BUGS] Fwd: Bug#249083: postgresql: Postgres SIGSEGV if wins in nsswitch.conf

Hi PostgreSQL developers! Does anybody happen to use Postgresql with winbind authentication? We got the bug report below where this seems to crash. Is this problem known? Thanks and have a nice day! Martin - Forwarded message from Cory Dodt <[EMAIL PROTECTED]> - Subject: Bug#249083: p

Re: [BUGS] Fwd: Bug#249083: postgresql: Postgres SIGSEGV if wins

Martin Pitt wrote: Hi PostgreSQL developers! Does anybody happen to use Postgresql with winbind authentication? We got the bug report below where this seems to crash. Is this problem known? Subject: Bug#249083: postgresql: Postgres SIGSEGV if wins in nsswitch.conf Reply-To: Cory Dodt <[EMAIL PROTE

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

Martin Pitt <[EMAIL PROTECTED]> writes: > 2004-05-14 14:50:14 [8725] LOG: authentication file token too long, skippi= > ng: "=98.=ED=F1 > Segmentation fault Looking at the only place this message is produced, in src/backend/libpq/hba.c, it appears that we are printing a string buffer that is not

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

I said: > I would suggest adding more paranoia along these lines: 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.