On 10/5/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > The user can only call methods on the objects you pass to the template > via the context. So if you want to restrict what they can do, only pass > in objects that have the methods you want to permit. This is exactly why > this method of function calling isn't any kind of security problem: the > view writer has precise control over what resources are supplied to > template authors.
Although the problem of opening up the Django template language to arbitrary users runs much deeper; a site administrator needs to be *very* careful not only about what's passed in the context, but also about context processors and available tag libraries. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
