On 12/12/2010 08:19 PM, Gabriel Petchesi wrote:
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.
Yes, you are right, I have tried it and it gives me an error about the
permissions of the file. But, what is the "web process"? the www-data
user? You say also "depending n your setup", so is there any setup
process that allow to configure the permissions to the security files?
Im just curious..
2. Cleaning the cache after each update
You have to clear up the symfony cache after each update to the
security.yml files.
I'm not sure if you're right..I didn't need to do "cc" to change the
credentials of an action.
sf 1.4/propel
Javier
--
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
