Conflict with SSL

Mark Malkasian
Fri, 5 May 2000 21:42:12 -0400

>[Friday, 05/05/2000] Mark Malkasian:
> > gpg: failed to create temporary file
> > `/www69/web/myaccount/cgi-local/.gnupg/.#lk100d2918.www69.22793859':
> > Permission denied
> > gpg: fatal: /www69/web/myaccount/cgi-local/.gnupg/trustdb.gpg: can't
> > create lock
> > secmem usage: 1408/1408 bytes in 2/2 blocks of pool 1408/16384
> >
>My guess is that your CGI script runs under a different UID with and
>without SSL.
>A possible solution: find out what UID the CGI script runs under SSL
>(I wouldn't be surprised if it where 'nobody') and make your trustdb.gpg
>file readable/writable by that UID, just before issuing the GPG command
>(and restoring its permissions after the command finishes)
>Good luck.
You were definitely on the right track. I needed to change the ownership of the gpg executable, configuration files, and the directory in which they're stored, as well as the directory holding the encrypted files, to "web". For ex., $how_many = chown ("202", "103 103", "$root/cgi-local/.gnupg", $root/cgi-local/. gnupg/gpg", etc); Of course, the permissions for the directory to which encrypted files are written has to be 0777. Thanks, Mark Malkasian ------------------------- Mark Malkasian