I would change: 
# Encrypt file.
my $gpg_command = `gpg --trust-model always -er 12345678 my_file.txt`;
print defined($gpg_command) ? $gpg_command : "Command failed\n";

# Capture STDOUT and save it to a file.
open(READ, "$gpg_command 2>&1 |") or die "Failure on open $!\n";

 open( my $out, ">", "encrypted.pgp" ) or die "Could not open file for
+ encrypted data - $!";

[download]

to: 

# Build encryption command
my $gpg_command = "gpg --trust-model always -er 12345678 my_file.txt";

# Execute command and capture STDOUT.
my $gpg_results = `$gpg_command`;
print defined($gpg_results) ? $gpg_results : "Command failed\n";

# Save captured STDOUT to a file.
open( my $out, ">", "encrypted.pgp" ) or die "Could not open file for 
+encrypted data - $!";

[download]

Then:

In reply to Re: Capture response from backticks to a file. by marinersk
in thread Capture response from backticks to a file. 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.