You may want to set up a global variable with all of your default gpg parameters.
Examples:

our $GPG = qq|/usr/local/bin/gpg --no-version --comment "" --no-secmem
+-warning --no-permission-warning --homedir "./.gnupg" --no-tty|;
# List keys
my $cmd = qq|$GPG --fingerprint --list--keys --with-colons|;
# Delete specific key
my $cmd = qq|$GPG --delete-secret-and-public-keys 0x$Fingerprint|;
# etc. etc. etc.
#
my $Result = qx|$cmd|; my @PGPKeys = split(/\n/,$Result);
# Do something . . .

[download]

Move or delete the 'homedir' directory, and then use only perl script(s) to work with the gpg entries. I don't know if this will work with windows, but it worked for me on all versions of *nix I tested. All permissions will be set up correctly.

Hopefully, this will get you going.

Good Luck

"Well done is better than well said." - Benjamin Franklin

In reply to Re: bad gpg by flexvault
in thread bad gpg by cmac

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.