--logger-fd n in Windows Visual Basic

David Hill DHill at StudentLoan.org
Wed Jun 9 20:31:53 CEST 2004

Alright, I've beaten myself bloody trying to figure this out, I haven't found anything in the archives, time to give up and ask for help.
I am working in Windows, programming in Visual Basic and I need to use GnuPG to encrypt and sign files, decrypt files, and verify signatures. Encryption and decryption is cake, but getting access to stderr to get key information is killing me. So THEN I thought I'd just do the key check in a separate step from the decryption command, I piped output from --list-packets to an --output file. As you might guess, no output file is created even though the only output of --list-packets is the packet information, probably went to stderr instead of my file.
I've put together a simple ActiveX dll that creates and shells batch files to interface with GnuPG. Apparently I can redirect the non-file output by using --logger-fd and giving it a file descriptor number. An interesting method of naming an output file, personally I might have recommended a command line file name much like --output uses, but let's get past that for now. Can anyone tell me how to create a file descriptor in Windows that this thing will accept? Is there an API that I should use to allocate/deallocate a file descriptor?
GPGME looked like an interesting alternative to rolling my own interface, unfortunately it doesn't come compiled, only as a big pile of source code. Also couldn't find any compatibility statement that indicated it would even work if I tried to compile and use it in Windows. Rolling my own for the few functions I needed probably took less time than getting a GPGME compile to run, if only there were a rational way to access the stderr information.
Dave Hill
dhill at studentloan.org
Iowa Student Loan Liquidity Corp.
Fax 515-243-0714
-------------- next part --------------
An HTML attachment was scrubbed...
URL: /pipermail/attachments/20040609/3fd867b0/attachment.html

More information about the Gnupg-users mailing list