Perl Open having problem when called from web.

[pablocruise77]

We have two Perl script that use the open command to read an encrypted file. We just changed from gzip to gpg. One script works fine. The other is called from the web and fails on the open.

Both run on UNIX hosts running SunOS 5.9 and Perl 5.8.8.

To debug, I scaled down the problem script to something called testread4.pl. When I run it from the UNIX command prompt, it works fine. It opens the encrypted file and returns 10 line of output. When I call it from the webpage, it shows nothing in the browser. Checking the error_log file, it says:

gpg: cannot open `/dev/tty': No such device or address

It seems like from the web, its not getting all the UNIX environment variables and doesn't recognize /dev/tty.

The code is below:

http://ourhost:8000/cgi-bin/test4.cgi

cat test4.cgi

#!/usr/bin/ksh
. /home/apache1/.profile
./testread4.pl
 

cat testread4.pl

#!/usr/local/bin/perl -w
 
$gpgPassFile = 'password';
$fileWithPath= 'test.gpg';
 
$dataMax=10;
 
print "Start of file read\n";
 
        open(FILE, "gpg --passphrase-file $gpgPassFile --decrypt $fileWithPath | " ) ||
             die("Unable to open $fileWithPath with gpg!");
 
        $x=0;
 
        while (<FILE>) {
                print "<tt> $_\n";
                if ($x >= $dataMax) {
                    last;
                }
        }
        close(FILE);
 
print "End of file read\n";
 

Any ideas?

[KevinADC]

change this:

die("Unable to open $fileWithPath with gpg!");

to:

die("Unable to open $fileWithPath with gpg!: $!");

and you should get a better error description. Probably "permission denied" or "can't find file"

You might try a full path to pgp:

'/usr/bin/gpg --passphrase-file $gpgPassFile --decrypt $fileWithPath |'

or whatever the path is.

[pablocruise77]

Made the changes you suggested. What's interesting is that it's not dying. I put some debug msgs before and after the open. It makes it past the open but it outputs nothing except the debug msgs.

[KevinADC]

I'm not sure what the problem is then. Can you run the perl script directly instead of uing ksh?

[pablocruise77]

Solved it. Did a google for the error and found that others had encountered it as well. If I add the option --no-tty to the gpg command and add 2>/dev/null to the end, the former gets rid of the /dev/tty error while the latter gets rid of any error messages that the gpg generates.

Thanks for all the help!