#!/opt/perl/bin/perl -w

#use strict;
use GnuPG qw( :algo );

my $gpg = GnuPG->new(gnupg_path => "/usr/local/bin/gpg", homedir => "/
+home/rolivier/.gnupg");

my $encfile='/home/ro/big.testfile.gpg';
$outfile = $encfile;
$outfile =~ s/.gpg//;
my $pp='Passphrase';

$gpg->decrypt(ciphertext => $encfile, output => $outfile, passphrase =
+> $pp);
[download]

The program I'm writing will be processing thousands of small files, so repeatedly calling an external process isn't the best solution. That's why I was looking for a pure-perl implementation.

If the module already calls /usr/local/bin/gpg externally, then you have a different problem. You need to be sure that you are not creating a new Crypt::OpenPGP object for each file, otherwise you will be causing alot of overhead. What you want to do is create 1 Crypt::OpenPGP object and reuse it. You must clear out all the old data in the object after each use. See

7.27: How do I clear a package?

    Use this code, provided by Mark-Jason Dominus:

        sub scrub_package {
            no strict 'refs';
            my $pack = shift;
            die "Shouldn't delete main package"
                if $pack eq "" || $pack eq "main";
            my $stash = *{$pack . '::'}{HASH};
            my $name;
            foreach $name (keys %$stash) {
                my $fullname = $pack . '::' . $name;
                # Get rid of everything with that name.
                undef $$fullname;
                undef @$fullname;
                undef %$fullname;
                undef &$fullname;
                undef *$fullname;
            }
        }

    Or, if you're using a recent release of Perl, you can just use the
    Symbol::delete_package() function instead.
[download]

So now you can reuse that same opening of /usr/local/bin/gpg, which will speed things up and reduce memory usage. You would still have 1 memory problem however, because the perl object's memory usage will swell to the largest file size it encounters.

So you may have to filter your files for size, to decide to feed them directly to the binary, or use the reusable module.

There is also the possibility of running parallel processes in threads if you have a multicore computer. But that is a whole different thread on it's own, running gpg thru threads.

1 last bit of advice, run all your decoding on a ramdisk if it is to be kept private. :-)

---

I'm not really a human, but I play one on earth. ..... an animated JAPH