RICHARD FERNANDEZ wrote:
[...]
It decrypts my file successfully. But if I break up the arguments
like it says in the doco, like so:
my @gpg_command = ("/usr/bin/gpg", "--decrypt", $encrypted, ">",
$decrypted, "2> /dev/null");
AFAIK, you can't use "2> file" to do output redirection when
> I would suggest giving GnuPG::Interface a go because it
> handled calling out to 'gpg' most "correctly". Meaning it
> uses the status-fd, logger-fd options properly which is the
> preferred way to call gpg in an automated fashion.
>
> Good luck,
>
> http://danconia.org
>
Thank you! I will
RICHARD FERNANDEZ wrote:
> I re-wrote the decryption routine to use system instead of Crypt::GPG,
> and came across another puzzle:
>
> my @gpg_command = ("/usr/bin/gpg --decrypt $encrypted >
> $decrypted 2> /dev/null");
> system(@gpg_command) == 0 or warn "system @gpg_command failed:
I re-wrote the decryption routine to use system instead of Crypt::GPG,
and came across another puzzle:
my @gpg_command = ("/usr/bin/gpg --decrypt $encrypted >
$decrypted 2> /dev/null");
system(@gpg_command) == 0 or warn "system @gpg_command failed:
$!";
works. It decrypts my file
Hi folks,
I have the following function:
sub lbx_decrypt {
my $encrypted = shift or die "No file passed in to lbx_decrypt for
decryption?\n";
my $decrypted = substr $encrypted, 4;
$decrypted .= '.zip';
my $gpg = new Crypt::GPG;
$gpg -> gpgbin('/usr/bin/gpg');
open CIPHERTXT
