This probably won't solve your problem but I don't think you need to explicitly open STDOUT & STDERR with IPC::Open3, I haven't used pgp but aside from a problem with pgp accepting the input (as BrowserUk showed) this should also work and is a bit simpler- 
# example open3() code only
  my $pgp_command = "pgp --key-add temp_pgp_key.asc --with-private";
  open3(*PGP_IN, *PGP_OUT, *ERROR, $pgp_command);
  print PGP_IN "\n";
  close(PGP_IN);
  my @return = <PGP_OUT>;
  close(PGP_OUT);
  my @error=<ERROR>;
  close(ERROR);

[download]

--
Until you've lost your reputation, you never realize what a burden it was or what freedom really is. -Margaret Mitchell

In reply to Re: Open3 with STDIN STDOUT and STDERR by greenFox
in thread Open3 with STDIN STDOUT and STDERR by Anonymous Monk

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.