2009/9/2 Kenneth Gonsalves <law...@thenilgiris.com>: > > On Tuesday 01 Sep 2009 10:55:18 pm mrsource wrote: >> - It has many tools for safety, with a normal opensource CMS you have >> many more issues with security holes because all the code is public. > > this is sheer FUD to say that 'many more issues with security holes because > all the code is public.' Openssl code is public, linux code is public, apache > code is public ... does one have many more issues with security holes???
That was my first thought, but I think he means that unlike standard PHP, you don't have to place your django files in /var/www, where bad configuration might expose your code. But still, bad argument. --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
