installing GPG contrib

[kerrydax]

Hello,
I am trying to install the GPG contrib to encryt credit card numbers for offline processing.
OK so I have generated the keys using CPanel and editied the ccgpg.php file to point to the public key and the temp directory I made (with write permissions).

But my question is, where do I put the ccgpg.php files so it is recognised by oscommerce? In the main directory or in the payment modules directory? I have tried both to no avail. What module to I "turn on" in the admin section to enable GPG?

The instructions that come with the contrib are a little vague.
Thanks in advance.
Kerry

[jpf]

Which One?
GPG Credit Card Encryption
http://www.oscommerce.com/community/contributions,611

GPG Credit Card Encryption 0.94 english
http://www.oscommerce.com/community/contributions,894

Secure Credit Card - GPG
http://www.oscommerce.com/community/contributions,2013

[kerrydax]

Hi,
I am trying to install GPG Credit Card Encryption at
http://www.oscommerce.com/community/contributions,611
Cheers,
Kerry

[michael_s]

ccgpg.php goes in /catalog/includes/modules/payment dir.

You should then also REMOVE the default credit card module from that dir (cc.php) to avoid confusion. Then from the admin, enable Credit Card. It will be the GPG module...

[kerrydax]

Thanks for your help. I got the module enabled but now I have a different problem. I get all the way through the checkout process until the last step (confirm order). When confirm order is clicked I get a "page cannot be found" error. The URL is https://gravitycomputers.com.au/stor...ut_process.php (and yes, the file exists on the server). It puts a file in the temp directory with the order number and unencrypted credit card number, but that's as far as it goes. There are no error messages. Does anyone have any ideas about what could be going on?

Also, I notice in the contrib zip file, the file modules.php. Am I supposed to put this somewhere on the server?

Thanks for all your help!!

[kerrydax]

As far as I can tell (with my very limited scripting knowledge) is that it is having problems with the line
system("export HOME=".$gpghome.";".$gpgpath." --verbose --verbose -r '".$gpgrecipient."' --encrypt -a -z 0 ".$plainTxt." ");

It does get to the stage of writing the card number and order number to a file, but does not get past the above command and does not delete the temp files either! (which are in the lines below the command) Does anyone have any ideas? thanks in advance! Kerry

[jpf]

Did you set the following?:

$gpghome="/home/useraccount"; //where is your pubring? That dir has to have write access.
$gpgpath="/usr/bin/gpg"; //where is the executable
$gpgrecipient="blib@useraccount.com"; //the key used for encryption


to somthing vaild for your server?

See the included file GPG_Cpanel_setup.txt for more information....

[michael_s]

Also, check your error logs. It should tell you where the script is bombing out if there is a php or permissions problem...

[kerrydax]

Thanks for your time..

the $plainTxt variable I have set as "/home/gravity/public_html/store/temp/" same with the $crypted variable. I know these are valid because the script is, in fact, writing a file to the temp directory.
$gpghome I have set to "/home/gravity" I wasn't sure whether to put it as /home/gravity/.gnupg, but I have tried both to no avail.

The $gpgpath="/usr/bin/gpg";
and the $gpgrecipient="Kerry de Vent (Gravity Computers) <sales@gravitycomputers.com.au>"

So I don't see any problems with these variables. The error logs are not showing anything so I am tearing my hair out trying to find the cause of this... I have set the permissions of the .gnupg directory and all the files in it to 777 temporarily (when it is working I will tighten the permissions), also the temp directory is set to 777. Are there any other permissions that need to be set to read/write access? Thanks.

[michael_s]

Most likely this is a completely separate issue. Check your configure.php and tweak the paths. If you are using shared ssl, that is most likely the cause. Try adding the full url to your shared ssl directory, and make sure your cookie paths and all other dir paths match...