[ANNOUNCE] Django security releases issued: 1.9.3 and 1.8.10
53 views
Skip to first unread message
Tim Graham
unread,
Mar 1, 2016, 12:20:27 PM3/1/16
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to django-announce, django-d...@googlegroups.com, django...@googlegroups.com, oss-se...@lists.openwall.com
Today the Django team issued 1.9.3 and 1.8.10 as part of our security process. This releases address two security issues, and we encourage all users to upgrade as soon as possible.
Details are available on the Django project weblog:
As a reminder, we ask that potential security issues be reported via private email to secu...@djangoproject.com and not via Django's Trac instance or the django-developers list. Please see https://www.djangoproject.com/security for further information.
José David Ordoñez
unread,
Mar 2, 2016, 8:49:03 PM3/2/16
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Django users
After upgrading django 1.8.9 to 1.8.10 my i18n/setlang/ went crazy "TypeError: must be unicode not str" when using {% url 'set_language' %} by going back to 1.8.9 solved the issue.
Tim Graham
unread,
Mar 2, 2016, 10:00:34 PM3/2/16
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Django users
Please create a separate thread with some details such as a sample project with steps to reproduce the issue so we can determine if it's a problem in Django or in your application. Thanks!