PHP + PGP

Anon

I have problem runing the "PGP to File" script:

putenv("PGPPATH=/path/to/.pgp");

$clear = "/path/to/input_file";
$clear .="$time";

$crypted = "path/to/output_file";
$crypted .="$time";

$fp = fopen("$clear", "w+");
fputs($fp, $msg);
fclose($fp);

system("/usr/local/bin/pgpe -r 'key_name' -o $crypted -a $clear");

$fd = fopen($crypted, "r");
$mail_cont = fread($fd, filesize($crypted));
fclose($fd);

As a result I do not have crypted file, but instead I can see the message how to use pgpe, and warning that no crypted file or directory found.

Any ideas why it does not work?

Thank you.

Anon

I made a mistake, the correct is:

"As a result I do not have crypted file, but instead I can see the message how to use pgpe, and warning that no crypted file or directory NOT found."

I tested the command in SSH mode and it works...

Anon

I don't see anything terribly wrong. My code is very similar.

I assume you have the correct paths. I notice that $crypted does not have a leading / .

Neither path has a trailing / . So your files may not be landing in the folder you expect (and you may not have write permission for that folder). For example, your code about would write a file to /path/to/input_file### (where ### is the time). Instead you may be wanting /path/to/input_file/###.

Are the paths to the input and output files different? If they are not, you might not be able to write to your output file since it may have the same name as your input file.

I also notice that there are quotes around $clear in fopen("$clear", "w+"); . But not around $crypted in fopen($crypted, "r"); . I don't know if that matters.

Using popen might be better since clear text isn't being written to disk:
$pp = popen("/usr/local/bin/pgpe -fat -r $pgp_key_array[$send_to] -o $msg_crypted","w");
fwrite($pp, $msgtext);
pclose($pp);

Instead of $time, you might want to use something like md5(uniqid(rand())) just in case two calls to this routine happen at the same time.

Just some thoughts. Let us know what happens.

Rob

Anon

I think I made the shortest script I could:

<?
//There are some words in the 'input_file'
//All rights are given to "/home/mydirectory/my_site-www/test/"

putenv("PGPPATH=/home/my_directory/.pgp");

$clear = "/home/mydirectory/my_site-wwww/test/input_file";

$crypted = "/home/mydirectory/my_site-www/test/";

$crypted .= $time;

system("/usr/local/bin/pgpe -r $pgp_key_array[$send_to] -o $crypted -a $clear");
?>

After executing this script you will see again the description how to use pgpe and the warning that path to crypted file is not found... The problem remains even if to create an output file and to give all rights to it. The only difference is that there is no message saying that the output file is not found.

P.S. I did all steps mentioned on http://hotwired.lycos.com/webmonkey/00/20/index3a_page3.html?tw=programming. In SSH mode it works well.

Anon

I don't see any problems.

Maybe try hardcoding the key id and the paths into the system call. For example:

system("/usr/local/bin/pgpe -r 0x12345678 -o /home/mydirectory/my_site-www/test/output_file -a /home/mydirectory/my_site-wwww/test/input_file");

I don't remember if the key id (which I've put in as 0x12345678) and the paths have to be within single qoutes. Try both ways, I guess.

If that starts working, then you can put the variables back in.

Julie's article at webmonkeys is a great place to start.

Rob

Anon

Using 'pgpk -l' command in SHH mode I wrote the key ID. Then I did hardcoding with single qoutes and without qoutes of key_id and paths to input and output files. Unfortunately, result is the same...

May be something wrong with Apache?

Anon

I don't know what the problem might be.

If you are hosting with a commercial provider, would they have a perl script that runs? If so, perhaps you could get that running, then strip it down to just few lines required to execute pgp. You could then use 'exec' to call that stripped down perl routine.

Its certainly not the most elegant solution, but it might get things working. It might also provide some insight into getting a pure PHP script working.

Rob

Anon

Hi,
A reply so long after the initial thread. Recently encountered exactly this problem. Take the code and rename file to .cgi and put the usual #! and file permissions in/on it and it works fine. Makes me think that a configuration problem, or restriction, is stopping the php script from correctly setting the environment variable that pgp needs. However in cgi mode, with/without suExec, the variable gets set ok and the script is happy.

Paul

Anon

Am I glad to hear that!

This is still a struggle, so don't worry about the late reply.

What I now need to do is call the cgi script just to do the encryption and then go back to an ordinary php file. The reason for that is that I am a 'co-worker' I do the php stuff and someone else does the web page design and layout and they want to use Dreamweaver.

But I'm a bit novice at this! So to call the cgi file correctly would this be in the right direction?

function encryptccdetails($msg)
{
exec("http://www.reservationsnetwork.ie/test/respag/encnew1.cgi","crypted");
return crypted;
}

encryptccdetails is passed the text to encrypt in msg

then the exec passes it back as "crypted"

and then the functon returns the variable crypted

I've not done an exec before and I found the manual confusing.

Regards and thanks

Elizabeth

Anon

Hi,

Am I glad to hear that!

Erm... kind of strange this, but erm.. I am the person replying to your support queries, positive internet? 😉

This is still a struggle, so don't worry
about the late reply.

:-)

But I'm a bit novice at this! So to call
the cgi file correctly would this be in the
right direction?

Ok, easiest option is to run any script that needs to use pgp in cgi mode. We have since verified that the main problem is that php will not let you set environment variables (for security reasons). CGI mode will but only because we use suExec. So the full answer is:

Put this at the top:
#!/usr/local/bin/php
Rename to .cgi and check permissions are 755 or 700 (executable).
Force saving of the file locally into unix format and upload in ascii mode.

If you get an internal server error the script has probably got corrupted by uploading in binary or from having dos's dodgy cr/lf's.

It is a real shame that there is no way to get pgp to pick up the home dir from anywhere else but env variables. I figure this could be security but sure an env variable is easy enough to fake on a system....

Paul