> and besides, cake programmers are programmers too... i've inspected the
> cake code and that's why i *know* that cake handles stuff like sql
> injections, session hijackings,.. also, it provides very easy ways for
> the programmer to protect himself against XSS and the like.
We also cover CSRF,
>
> Security is the responsibility of the PROGRAMMER, not the framework.
> The best security features are not worth anything if you don't use
> them properly.
>
> All the common security problems like XSS, cross-domain scripting and
> SQL injection are easily solved by the programmer. Expecting
On 11/13/06, Ger_Val <[EMAIL PROTECTED]> wrote:
>
> Hi! I'm new to CakePHP, seems it's a really great framework. I didn't
> find any bad comments about it in the Internet. Probably, I was looking
> badly. :)
> What about using CakePHP for large projects? My concerns are about
> performance and sec
Cakephp, combined with a decent auth system (check the bakery for that)
will do pretty much everything they can to make your app as secure as
possible. (sql injections, session hijackings, brute force attempts,
network sniffings...)
http://bakery.cakephp.org/articles/view/147 will address al thes
Hi! I'm new to CakePHP, seems it's a really great framework. I didn't
find any bad comments about it in the Internet. Probably, I was looking
badly. :)
What about using CakePHP for large projects? My concerns are about
performance and security. I've read some posts and people say
performance is no
