I was testing some old GnuPG scripts today, with my latest version of GnuPrivacyGuard ( version 1.42 ) and found a little easy to fix bug. Since the module appears to be unmaintained anymore, I'll mention it here.

First, it has been previously known, that a "strict" bugfix was to change line 267 of GnuPG.pm to avoid the 'bareword not allowed while using strict' error

# from
 my $max_fd = POSIX::sysconf( POSIX::_SC_OPEN_MAX  ) || 256;

# to
    my $max_fd = POSIX::sysconf( POSIX::_SC_OPEN_MAX()  ) || 256;
[download]

Second, when you use versions of gpg > 1.25 (according to a debian bug report) with GnuPG.pm, you will get a decrypt error:

protocol error: expected DECRYPTION_OKAY got PLAINTEXT:
[download]

So another fix is to change GnuPG.pm, at line 742

# from
#    $self->abort_gnupg( "protocol error: expected DECRYPTION_OKAY got
+ $cmd: \n" ) 
#      unless $cmd =~ /DECRYPTION_OKAY/; 

# to
    $self->abort_gnupg( "protocol error: expected PLAINTEXT got $cmd: 
+\n" )
      unless $cmd =~ /PLAINTEXT/;
[download]