diff options
| author | Bruce Momjian <bruce@momjian.us> | 1998-08-22 04:49:05 +0000 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 1998-08-22 04:49:05 +0000 |
| commit | 99a099d436a35230a39e21012af74d714faef762 (patch) | |
| tree | aa9c893ae148fba238ff11073318ea9527e48bcf /src/backend/parser/parse_target.c | |
| parent | c0d730460fc93ae83a50a5375b843ccb9b020e66 (diff) | |
| download | postgresql-99a099d436a35230a39e21012af74d714faef762.tar.gz postgresql-99a099d436a35230a39e21012af74d714faef762.zip | |
With the attached patch, I have verified that long (> 8char anyway)
usernames and passwords work correctly in both "password" and
"crypt" authorization mode. NOTE: at least on my machine, it seems
that the crypt() routines ignore the part of the password beyond
8 characters, so there's no security gain from longer passwords in
crypt auth mode. But they don't fail.
The login-related part of psql has apparently not been touched
since roughly the fall of Rome ;-). It was going through huge
pushups to get around the lack of username/login parameters to
PQsetdb. I don't know when PQsetdbLogin was added to libpq, but
it's there now ... so I was able to rip out quite a lot of crufty
code while I was at it.
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.
regards, tom lane
Diffstat (limited to 'src/backend/parser/parse_target.c')
0 files changed, 0 insertions, 0 deletions