Skip Menu |

This queue is for tickets about the GnuPG-Interface CPAN distribution.

Report information
The Basics
Id: 133041
Status: open
Priority: 0/
Queue: GnuPG-Interface

People
Owner: Nobody in particular
Requestors: PUCK [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 1.00
Fixed in: (no value)



Subject: GnuPG::Interface causes programs running in Taint mode to fail due to $ENV{PATH} being tainted
Hey, After we uploaded GnuPG::Interface v1.0 to Debian, several Perl programs that run with Taint mode failed to run, for example: https://bugs.debian.org/964878 This is because GnuPG::Interface uses $ENV{PATH} which is tainted. I propose resolving this by detecting if Taint mode is enabled and un-setting the path. This requires that the full path to a gpg binary is provided. I'm resolving this in Debian by changing the default from 'gpg' to '/usr/bin/gpg'. The proposed patch (minus changing the default binary) is attached. Cheers, Andrew
Subject: detect-taint-mode
Download detect-taint-mode
application/octet-stream 496b

Message body not shown because it is not plain text.

Attached is a test file to test that GnuPG::Interface can run in Taint mode.
Subject: taint.t
#!/usr/bin/perl -wT # # Ensure we can instatiate in Taint mode. Don't need to # do any work, as GnuPG::Interface runs the command we're going # to use to detect the version. use strict; use lib './t'; use MyTest; use GnuPG::Interface; my $gnupg; # See that we instantiate an object in Taint mode TEST { $gnupg = GnuPG::Interface->new( call => '/usr/bin/gpg' ); }; # See that version is set TEST { defined $gnupg->version; };
Hi, I've applied a very similar patch to yours on this branch: https://github.com/bestpractical/gnupg-interface/tree/update-version-if-call-is-updated Does it fix it for you? Regards, Dianne.
Sorry, this is the wrong ticket; please ignore.