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;
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:
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/;
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.