From: | Euler Taveira de Oliveira <euler(at)timbira(dot)com> |
---|---|
To: | agrimm(at)gmail(dot)com, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #6412: psql & fe-connect truncate passwords |
Date: | 2012-01-28 16:55:46 |
Message-ID: | 4F242892.50403@timbira.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 27-01-2012 23:15, agrimm(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Andy Grimm | 2012-01-28 17:32:24 | Re: BUG #6412: psql & fe-connect truncate passwords |
Previous Message | james | 2012-01-28 16:16:47 | BUG #6413: pg_relation_size wont work on table with upper case chars |