Re: [cms-users] Overwrite protection + some suggestions

[Roger B. <ro...@sa...>]

Hi Alexandre,

Alexandre Gravel wrote:
 
> I'm not sure how the API will work yet. Should we work on a temporary
> release with the submitted patches or get our heads down to the API-ready
> release ?

I don't know enough about coding to be much help, so I'll I'll leave the
answere to this question to you and\or others

> Roger Buck wrote:
> > I think there should also be a configurable way to limit the hosts that
> > the script can can validly be run from (limit referers).
> 
> That could  be easily done with a simple text file that contains the allowed
> hosts or disallowed hosts. The check could be done at every execution of the
> script.

OK - Also see attached code - this was stolen from something I once saw
in a script at at http://www.bignosebird.com/ (sorry I can't remember
the name of the script).
 
> > Would be nice if the crm generated admin files were kept out of the main
> > folder (maybe simply created in a separate, parallel, tree structure -
> > this could be done easily using a configurable path variable prefix in
> > the crm.cgi?
> 
> By admin files, do you mean the logfile ?

No, what I mean is the files currently generated by cms (such as
*.comment  *.reason and so on..) that are placed in the same folder as
the file(s) that cms is designed to manage:

What I was thinking of was having two paralell file systems:

 folder1 is where all the normal userspace file are stored (the current
cms variable $filepath)

 folder2 would be in a separate, paralel tree - say $cmspath.$filepath,
where $cmspath is a constat that would be configured by the site admin

Does that make any sense? :-)  

R.

Here's the example referer stuff: