-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
From: Maury Markowitz
Date: Fri, 29 Feb 2008 15:10:47 -0500
Subject: _almost_ working, now a command line question...
All that's left now is to fully automate this, and my Windows CMD
noobishness is an issue. Here's my command line:
O:\Utilities>echo o:\apricing\pass.txt | o:\utilities\gpg --homedir o:\utilities
\ --passphrase-fd 0 --load-extension o:\utilities\idea.dll -o "o:\apricing\morga
n_cds_20080229.txt" -d "o:\apricing\24476.txt.pgp"
And here are the results (slightly trimmed to protect the innocent):
Reading passphrase from file descriptor 0
You need a passphrase to unlock the secret key for
user: "Polar Securities Inc <[EMAIL PROTECTED]>"
2048-bit ELG-E key, ID 3E396FC9, created 2000-10-27 (main key ID F0ED5CDC)
gpg: encrypted with 2048-bit ELG-E key, [snip]
gpg: public key decryption failed: bad passphrase
pass.txt absolutely has the right key in it. I tried both | and >, the
later did nothing at all (which I guess makes sense).
Doesn't
echo o:\apricing\pass.txt
produce output of "o:\apricing\pass.txt"?
You might have better luck redirecting gpg's standard input from
pass.txt, like this:
o:\utilities\gpg
--homedir o:\utilities \
--passphrase-fd 0 \
--load-extension o:\utilities\idea.dll \
-o "o:\apricing\morgan_cds_20080229.txt" \
-d "o:\apricing\24476.txt.pgp" < o:\apricing\pass.txt
Also, be careful of extra whitespace in pass.txt.
Steve
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.8 (Darwin)
iEYEARECAAYFAkfIiyYACgkQX7YJI4BuyDQf0QCg2AUA0Bd/o6h7mI1RF4gswPYT
/uwAoLJGeBhHn62VHZA1LhCHhkIeVbPn
=oJI2
-----END PGP SIGNATURE-----
_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
