bad passphrase error passing it into GPG on Windows 98 using stdin

Leigh S. Jones, KR6X kr6x@kr6x.com
Wed Jun 26 23:21:02 2002


Right.  Well, this kind of question comes up so often that
it really needs to be approached by Werner.  You should
be able to pass a handle to a pipe to the Ming/W32 gpg
the same way that you do to gpg on Linux, without doing
a conversion with osf_filehandle().

But I may just put a program up here on the list that will
help with that.  Perhaps a tiny program in C that takes
a command line argument of a file descriptor and returns
an "osf_filehandle ( )" converted to a string at it's stdout.
Then a script could redirect the output to a variable.
It would be worth the effort just to be able to stop
answering these same questions over and over again.

----- Original Message -----
From: "Clough, Samuel" <Samuel_Clough@invesco.com>
To: "'Leigh S. Jones, KR6X'" <kr6x@kr6x.com>; <gnugpghelp@mlhp.net>
Cc: <gnupg-users@gnupg.org>
Sent: Wednesday, June 26, 2002 14:03
Subject: RE: bad passphrase error passing it into GPG on Windows 98 using
stdin


> I agree with what you are saying.  However, all I know is that on Windows
> NT, this is the only way I could get it to work with --passphrase-fd 0.  I
> would have preferred to use a proper file handle, but not having C
available
> at work and not being a C programmer, I could never find an api that VB
> could use to get the proper system level file handle, so I had to resort
to
> fd 0, and I tried piping and redirecting the password but for some reason
> the command line only interpreted redirecting the file correctly.  If
> someone has found a way to pipe the actual password to fd 0 on the command
> line in Windows, I would love to know how because I would obviously rather
> do that than write a temp file just to use for the password and then
destroy
> it.
> There is an example in the archives of "password | gpg --passphrase-fd 0
> etc....".  Maybe this works in Dos proper or on other Windows versions but
> it does not work on NT.
>
> > This is the wrong way to use --passphrase-fd.  Even
> > if you're using Linux, the option:
> >
> > --passphrase-fd 0
> >
> > tells gpg that the actual passphrase will be passed into
> > the gpg program through a pipe to port zero; here
> > "passwordfile.txt" would have to be the actual passphrase
> > rather than the name of the file containing the passphrase.
> >
> >
>