pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Christopher Browne <cbbrowne@acm.org>
To: pgsql-php@postgresql.org
Subject: Re: PostgreSQL Backup Script
Date: Fri, 01 Apr 2005 00:04:48 -0500
Message-ID: <m37jjn6qa7.fsf@knuth.cbbrowne.com> (raw)
References: <77b69d2105033120543ca670a7@mail.gmail.com>

vishalonlist@gmail.com ("Vishal Kashyap @ [SaiHertz]") wrote:
> I am stuck with database backup.
> While using pg_dump the utility asks for password but since I require
> this process to be automated the password prompt is giving me
> headaches
> is their any way by which can pass the password automatically.
> Like setting up a variable in php  which passes the password to the
> pg_dump utility on prompt this way the whole process of pg_dump would
> get automated.
> One obvious solution was to use .pgpass but it does not appeal me
> because it is again a security threat.
> any pointers or help may lead to unlocked secret.

You seem to be imagining that there can exist a way of storing some
form of a password in a fashion that allows automating these sorts of
things that _doesn't_ present an identical security threat to that
involved with .pgpass

It may take a bit of thinking about the problem to disabuse oneself of
such fantasies...
-- 
(reverse (concatenate 'string "gro.mca" "@" "enworbbc"))
http://linuxfinances.info/info/security.html
Rules of the Evil Overlord #125. "Should I actually decide to kill the
hero in  an elaborate escape-proof  deathtrap room (water  filling up,
sand pouring down, walls converging,  etc.) I will not leave him alone
five-to-ten  minutes  prior  to  "imminent" death,  but  will  instead
(finding a vantage point or  monitoring camera) stick around and enjoy
watching my adversary's demise." <http://www.eviloverlord.com/;



view thread (5+ messages)  latest in thread

Message-ID: <m37jjn6qa7.fsf@knuth.cbbrowne.com>
Permalink:  ../m37jjn6qa7.fsf@knuth.cbbrowne.com/
Also on:    postgresql.org/message-id/m37jjn6qa7.fsf@knuth.cbbrowne.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-php@postgresql.org
  Cc: cbbrowne@acm.org
  Subject: Re: PostgreSQL Backup Script
  In-Reply-To: <m37jjn6qa7.fsf@knuth.cbbrowne.com>
  References: <77b69d2105033120543ca670a7@mail.gmail.com> <m37jjn6qa7.fsf@knuth.cbbrowne.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox