using verify over stdin

[David Shaw]

On Tue, Nov 05, 2002 at 01:11:34PM -0800, Justin Karneges wrote:
> On Tuesday 05 November 2002 05:14 am, David Shaw wrote:
> > On Tue, Nov 05, 2002 at 02:07:54AM -0800, Justin Karneges wrote:
> > > Thanks! :)
> > >
> > > Now one last problem.  Why when I use --passphrase-fd, it blocks program
> > > execution even though it has not sent NEED_PASSPHRASE to the status-fd?
> > >
> > > My plan was to always use --passphrase-fd and have a pipe ready,
> > > just in case a particular operation needs a passphrase.
> >
> > --passphrase-fd is separate from --status-fd.  If you use
> > --passphrase-fd, it always (needed or not) reads the passphrase in
> > during startup.
> 
> So how do you read the passphrase "on-demand" ?  Or is this just not
> possible?
> 
> I don't want to prompt the user unless the status says "NEED_PASSPHRASE".

Use --command-fd.  When you get status NEED_PASSPHRASE, send the
passphrase on the command-fd.

David

-- 
   David Shaw  |  dshaw at jabberwocky.com  |  WWW http://www.jabberwocky.com/
+---------------------------------------------------------------------------+
   "There are two major products that come out of Berkeley: LSD and UNIX.
      We don't believe this to be a coincidence." - Jeremy S. Anderson