For me your proposal looks more complicated, think about the following problems:
1. No write access to the security.yml files Depending on your setup the web process may not access those file to update them. 2. Cleaning the cache after each update You have to clear up the symfony cache after each update to the security.yml files. Both can be resolved of course, my feeling is that the solution would not be as elegant as a smart security filter. gabriel -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
