News for hackers. Stuff that matters.
Re:Security advisory: Breach and Django by JshWright on Tuesday August 06, 2013 @10:45AM (#6166838)
>And i was trying to report it, but didn't find a contact/email.

How hard did you try? Django uses the industry standard security@ address for reporting security issues.

A quick googling results in this page pretty easily: https://docs.djangoproject.com/en/1.5/internals/security/

EDIT: I described the link as 'first' in the Google results, but that was because Google was being helpful and promoting a page I've visited a lot before... In reality, it's a few links down.

Re:Security advisory: Breach and Django by homakov on Tuesday August 06, 2013 @10:46AM (#6166848)
1) open https://www.djangoproject.com/ 2) find /contact/, /email/, user group
Re:Security advisory: Breach and Django by steveklabnik on Tuesday August 06, 2013 @10:56AM (#6166890)
I've never really looked at Django's site before, picked 'community' on the upper right, and it says

  > Report potential security issues in Django via private email to 
  > [email protected], and not via Django's Trac instance or the 
  > django-developers mailing list
Re:Security advisory: Breach and Django by JshWright on Tuesday August 06, 2013 @10:58AM (#6166906)
The community page (where all the mailing lists and contact addresses are listed) say:

>Report potential security issues in Django via private email to [email protected], and not via Django's Trac instance or the django-developers mailing list