RE: Announcement: Smarty 1.4.3 now available
| From: | Monte Ohrt | Date: | Wed, 20 Jun 2001 22:10:48 +0000 |
| Subject: | RE: Announcement: Smarty 1.4.3 now available | ||
| References: | 1 | Groups: | php.smarty.general |
| Request: | Send a blank email to php-smarty-general+get-912@lists.php.net to get a copy of this message | ||
Should Smarty be responsible for this security test? This is extra logic
that must be put into every template page and checked for on every
invocation of the script(s). It would hardly _ever_ be used, only when a
person specifially knows the URL to try. If you are worried about this
security, it should be your responsibility to move the directories out
of document root.
I guess I don't like the idea of the logic overhead put into Smarty
templates for such a small percentage of times it would actually be of
use. Does this sound unreasonable?
hans@linux.gelrevision.nl wrote:
>
> On 20-Jun-01 Monte Ohrt wrote:
> > One easy and secure method is to put directives in apache (or via
> > .htaccess) to disallow direct access to /configs, /templates and
> > /templates_c directories.
>
> That isn't an opion for us. phpReview will be distributed for all webservers.
>
> I suggest that a simple redirect could be something like:
>
> if (basename($PHP_SELF) == "file.tpl.php")
> {
> header( "location: some configurl");
> }
>
> I'm using it for all the classes I'm writing. The question is what kind of
> default value could be used, maybe the smarty site :).
>
> Regards,
>
> Hans
> --
>
> Linux : http://linux.gelrevision.nl/
> phpReview : http://phpReview.nl.linux.org/
> Boeken : http://nl.linux.org/boeken/
>
> ---
> You are currently subscribed to smarty as: monte@ispi.net
> To unsubscribe send a blank email to $subst('Email.Unsub')
> Visit Smarty's homepage at
> http://www.phpinsider.com/php/code/Smarty/
--
Monte Ohrt <monte@ispi.net>
http://www.ispi.net/