-----BEGIN PGP SIGNED MESSAGE-----
Make the cgi accessable as normal; but only allow referrer urls
that are in some "hotlist" trigger execution. Let anything else
get an error in return. This solution can be gotten around, but
whaddaya gonna do? Don't you trust the cgi to be publicly
accessable? Cookies were invented for good reason.
--sig--
OK, I admit it: My girlfriend's just an object to me.
Unfortunately, there is some information hiding, but
thankfully, she's fairly encapsulated, nicely modular, and
has a very well defined interface!
On Sat, 22 Apr 2000, Super Perez wrote:
> Im sorry if this is considered off topic. I have a virtual
> server and I have a cgi script in a directory different from the
> cgi-bin directory. I want to be able to keep people from
> accessing the cgi file directly but allowing my pages to access
> it and return the desired output. How do I do this? I can set
> permissions on the directory and on the file.
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv
iQCVAwUBOQJlS8K9HT/YfGeBAQFhXAQAmcVeJzuhauIr9hD9QLFgxnhdEyof2G36
+h5sIB4pa46h36mtcxSGF8LjYQvZcGEwM9g+LEOApTSefCFLTGzvh9LPkf8ZhsbW
CgiM9/B3Z/84ksIzz3aVaXVdzGhJ4dF3p6qiPIJHsMC2N2td+9oU4Nskce1XRJFV
DRqZG0RPjVQ=
=QIAg
-----END PGP SIGNATURE-----
-
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
