From: | "Bing Du" <bdu(at)iastate(dot)edu> |
---|---|
To: | "Richard Huxton" <dev(at)archonet(dot)com> |
Cc: | pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: catch password on Postgres server |
Date: | 2004-01-30 21:15:13 |
Message-ID: | 4296.129.186.197.127.1075497313.squirrel@mail.eng.iastate.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
Thanks very much, Richard, for your response. Yes, I've verified other
ODBC applications can connect fine using the same password. I'll try your
suggestions. I've not used C for many years.
Bing
> On Thursday 29 January 2004 19:42, Bing Du wrote:
>> Greetings,
>>
>> Postgres 7.4 running on RedHat 9.
>>
>> We are trying to migrate a MS SQL server based comertial application
>> software to a Postgres database. We know what password that application
>> uses to connect to the MS SQL database.
>
>> Is there anyway on the server side to
>> see what was submitted in the password field by the application from
>> the
>> client side?
>
> Don't think you can get to the password without changing the code. I can
> think
> of two options:
> 1. In src/backend/libpq/auth.c search for "echo password to logs" and
> change
> the ereport() to log the password rather than not to. Reply to this if C
> isn't your thing.
>
> 2. Use tcpdump -s 255 port 5432 and see what's going over the wire. You'd
> need
> to set plaintext passwords though.
>
> Before any of this though, make sure you can connect from Access using
> that
> password.
> --
> Richard Huxton
> Archonet Ltd
>
From | Date | Subject | |
---|---|---|---|
Next Message | Jon Willeke | 2004-01-30 22:46:40 | Re: where's the build environment for odbc |
Previous Message | Jon Willeke | 2004-01-30 21:08:16 | Re: Unicode support on Linux? |