I was thinking about this as well. I think that we should publish the assets under the normal js/images/css folders in a subdirectory with either the plugin name or a name the user has specified in the app.yml of the installing application.
Kind regards, Marijn On Jan 30, 2009, at 3:41 PM, Fabien Potencier wrote: > > This has been discussed previously, and we can definitely think about > this for symfony 1.3. Feel free to open a ticket and start the > discussion about what can be done about it. > > Fabien > > -- > Fabien Potencier > Sensio CEO - symfony lead developer > sensiolabs.com | symfony-project.com | aide-de-camp.org > Tél: +33 1 40 99 80 80 > > > Jonathan Franks wrote: >> I was just thinking about the way plugin web assets are published to >> the web directory under a folder with the name of the plugin and I >> thought maybe it was a bit of security risk?? Surely it exposes the >> fact that the system is built on symfony, the ORM used, and the >> plugins used. A security flaw in anyone of these components could >> then >> be exploited. >> >> I don't think its a particularly serious problem but I thought I'd >> mention it anyway. >> >> Regards >> Jonathan >> >>> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" 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-devs?hl=en -~----------~----~----~----~------~----~------~--~---
