Thread: DBD::Pg and .pgpass
Greetings, I'm trying to run a Perl script connecting to a PostgreSQL database via DBI and DBD::Pg as a cron job. I'm already using the .pgpass mechanism for managing md5 passwords on the client side and would like to use the same mechanism for connecting from the Perl script. This does not, however, appear to work. Passing either "" or undef for the password yields "no password supplied at <script> line <line>". Though I could (and probably will, as I'm under some time pressure here) easily hack in a .pgpass parser to the Perl script, this strikes me as unconscionably inelegant. Is there some magic I'm missing to get DBD::Pg to play nice with .pgpass, or is this a bug in DBD::Pg (1.21) or the Postgres (8.0.1) client side itself? Regards, Brian -- Brian H. Trammell / MTS, CERT/NetSA / <bht@cert.org> / 412.268.9748
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > I'm trying to run a Perl script connecting to a PostgreSQL database via > DBI and DBD::Pg as a cron job. I'm already using the .pgpass mechanism > for managing md5 passwords on the client side and would like to use the > same mechanism for connecting from the Perl script. This does not, > however, appear to work. Passing either "" or undef for the password > yields "no password supplied at <script> line <line>". I know that this was a libpq bug in the past (circa 2002) but I thought it had been fixed. I am ccing this to the hackers list to see if anyone can verify this. - -- Greg Sabino Mullane greg@turnstep.com PGP Key: 0x14964AC8 200505040905 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iD8DBQFCeMjQvJuQZxSWSsgRAhLjAKDwVc1nIHPaAQIME6XpRfQv9uif4wCgjk51 xGLEKTOf0S157j5halCHKNg= =T3wQ -----END PGP SIGNATURE-----