Re: BUG #6412: psql & fe-connect truncate passwords - Mailing list pgsql-bugs

From Euler Taveira de Oliveira
Subject Re: BUG #6412: psql & fe-connect truncate passwords
Date
Msg-id 4F242892.50403@timbira.com
Whole thread Raw
In response to BUG #6412: psql & fe-connect truncate passwords  (agrimm@gmail.com)
Responses Re: BUG #6412: psql & fe-connect truncate passwords  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: BUG #6412: psql & fe-connect truncate passwords  (Andy Grimm <agrimm@gmail.com>)
List pgsql-bugs
On 27-01-2012 23:15, agrimm@gmail.com wrote:
> When psql prompts for a password, it only reads the first 100 characters of
> the password.  The limit in fe-connect.c (for when .pgpass is used) is
> weirder, a seemingly arbitrary 320 bytes for all fields combined.  Other
> (postgresql-jdbc, PyGreSQL, etc.) have no problem with a 512-byte password.
> It would be nice to have these limits controlled by a constant, and for the
> command to give an error or warning when a password is truncated.
>
I don't see it as a bug but a limitation. Why do you need such a long
password? If you are not comfortable with this reasonable limit, look at
fe-connect.c -> PasswordFromFile() and change the LINELEN. More to the point,
AFAICS all of the PostgreSQL client prompts are limited to 100 bytes (look at
simple_prompt function); letting 220 bytes for host, port, database, and user.


--
   Euler Taveira de Oliveira - Timbira       http://www.timbira.com.br/
   PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento

pgsql-bugs by date:

Previous
From: Eric Borts
Date:
Subject: Re: Windows x86-64 One-Click Install (9.1.2-1, 9.0.6-1) hangs on "initialising the database cluster" (with work-around)
Next
From: Tom Lane
Date:
Subject: Re: BUG #6412: psql & fe-connect truncate passwords