Skip Menu |

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

Report information
The Basics
Id: 35473
Status: rejected
Priority: 0/
Queue: GnuPG-Interface

People
Owner: Nobody in particular
Requestors: lloy0076 [...] adam.com.au
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 0.36
Fixed in: (no value)



Subject: Enhancement: Ability to Specify "Which" GPG to Call
I use Solaris and my GPG is in an odd place: /opt/csw/bin/gpg Occasionally /opt/csw/bin fails to make its way into my PATH setting and GnuPG::Interface fails with: Can't exec "gpg": Permission denied at /opt/csw/share/perl/site_perl/GnuPG/Interface.pm line 321. exec() error: Permission denied at /opt/csw/share/perl/site_perl/GnuPG/Interface.pm line 321. Others should substitute "/opt/csw/share/perl/site_perl" for wherever the module gets installed. After putting in a "hack" to work out what it's up to, I found that it's doing this: gpg --homedir /home/lloy0076/.gnupg --armor --recipient test --encrypt [That was print "@command" to a file handle at line 320 btw] I therefore did this: # cd /usr/bin # ln -s /opt/csw/bin/gpg gpg ...and it worked. Therefore, I am wondering if: 1. It's possible to change how "gpg" is called * Useful for odd setups like mine * Possibly useful for the security paranoid [is the GPG we called really the one we wanted] 2. If so, how and although I've read the documentation, which documentation page have I missed? 3. If not, would this be a useful addition? I can see the "call => 'gpg'" in GnuGPG::Interface.pm but don't understand Class::MethodMaker enough to be able to work out how to change this prior to initialising the object. Thanks, DSL
Subject: Re: [rt.cpan.org #35473] Enhancement: Ability to Specify "Which" GPG to Call
Date: Mon, 28 Apr 2008 10:31:20 +0400
To: bug-GnuPG-Interface [...] rt.cpan.org
From: "Ruslan Zakirov" <ruz [...] bestpractical.com>
Try my $gnupg = GnuPG::Interface->new( call => '/path/to/gpg/executable' ); On Mon, Apr 28, 2008 at 10:08 AM, lloy0076@adam.com.au via RT <bug-GnuPG-Interface@rt.cpan.org> wrote: Show quoted text
> > Mon Apr 28 02:08:22 2008: Request 35473 was acted upon. > Transaction: Ticket created by lloy0076@adam.com.au > Queue: GnuPG-Interface > Subject: Enhancement: Ability to Specify "Which" GPG to Call > Broken in: 0.36 > Severity: Normal > Owner: Nobody > Requestors: lloy0076@adam.com.au > Status: new > Ticket <URL: http://rt.cpan.org/Ticket/Display.html?id=35473 > > > > > I use Solaris and my GPG is in an odd place: > > /opt/csw/bin/gpg > > Occasionally /opt/csw/bin fails to make its way into my PATH setting and > GnuPG::Interface fails with: > > Can't exec "gpg": Permission denied at > /opt/csw/share/perl/site_perl/GnuPG/Interface.pm line 321. > exec() error: Permission denied at > /opt/csw/share/perl/site_perl/GnuPG/Interface.pm line 321. > > Others should substitute "/opt/csw/share/perl/site_perl" for wherever > the module gets installed. After putting in a "hack" to work out what > it's up to, I found that it's doing this: > > gpg --homedir /home/lloy0076/.gnupg --armor --recipient test --encrypt > > [That was print "@command" to a file handle at line 320 btw] > > I therefore did this: > > # cd /usr/bin > # ln -s /opt/csw/bin/gpg gpg > > ...and it worked. > > Therefore, I am wondering if: > > 1. It's possible to change how "gpg" is called > > * Useful for odd setups like mine > * Possibly useful for the security paranoid > [is the GPG we called really the one we wanted] > > 2. If so, how and although I've read the documentation, which > documentation page have I missed? > > 3. If not, would this be a useful addition? > > I can see the "call => 'gpg'" in GnuGPG::Interface.pm but don't > understand Class::MethodMaker enough to be able to work out how to > change this prior to initialising the object. > > Thanks, > > DSL >
-- Best regards, Ruslan.
From: lloy0076 [...] adam.com.au
That last suggestion worked. Here's a proposed FAQ: --- =item My GPG is not on my path - how can I tell GnuPG::Interface where it is? If you're GPG executable is in I</opt/csw/bin/gpg>, pass a C<call> parameter to the new object like this: use GnuPG::Interface; my $gpg = GnuPG->new(call => "/opt/csw/bin"); -- DSL