Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6]) by hub.org (8.8.8/8.7.5) with ESMTP id SAA12287; Sun, 2 Aug 1998 18:40:36 -0400 (EDT) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id SAA22435; Sun, 2 Aug 1998 18:40:28 -0400 (EDT) To: M.Boekhold@et.tudelft.nl cc: M.Boekhold@ITS.TUDelft.NL, pgsql-hackers@postgreSQL.org, pgsql-interfaces@postgreSQL.org, pgsql-patches@postgreSQL.org Subject: Re: [INTERFACES] Re: [HACKERS] User authentication bug? In-reply-to: Your message of Sun, 2 Aug 1998 13:42:29 +0200 (MET DST) Date: Sun, 02 Aug 1998 18:40:28 -0400 Message-ID: <22433.902097628@sss.pgh.pa.us> From: Tom Lane Maarten Boekhold writes: > On Sat, 1 Aug 1998, Tom Lane wrote: >> It's possible that there are still bogus length limits on username >> or password in some of the other PostgreSQL user interfaces besides >> psql/libpq. I will leave it to other folks to check that code. > I think the perl-module behaves the same, but I'm not totally sure about > it. I have a script where passing a 9 chars username to PQconnectdb() > fails to connect to a backend, while if I truncate the username to 8 > chars it works. Hmm. What pgsql version are you using? A quick glance at src/interfaces/perl5 doesn't show any dependencies on username or password length in it --- it's just a very simple wrapper for libpq. regards, tom lane