An easy improvement from the NIST guidelines would be to increase the size of Django's common passwords list.
Django currently includes 1,000, the linked NIST summary suggests using 100,000 (!!). On Thu, Nov 24, 2016 at 3:03 AM, Erik Romijn <[email protected]> wrote: > Hello, > > Django has had password validation built in as of 1.9. As far as I can > see, all guidelines you refer to are already implemented there, and enabled > by default in new projects. Could you elaborate on what changes you think > we need to make? > > Erik > > On 23 Nov 2016, at 16:21, William Hakizimana <[email protected]> wrote: > > While we are at it, could we implement these NIST new password guidelines > <https://nakedsecurity.sophos.com/2016/08/18/nists-new-password-rules-what-you-need-to-know/> > into django? Just > > On Monday, November 21, 2016 at 3:13:21 PM UTC-6, Tim Graham wrote: >> >> We don't normally give security advisories for issues that affect only >> the master branch, but in this case we've made an exception as the issue >> could be high impact. >> >> Please see the blog post for details: >> https://www.djangoproject.com/weblog/2016/nov/21/passwordres >> etconfirmview-security-advisory/ >> > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/django-developers/71b646e9-9a39-4e47-9aa9- > c6cfacd82b6e%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/71b646e9-9a39-4e47-9aa9-c6cfacd82b6e%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/django-developers/0D5D730A-3C3E-4886-8C9C- > 3FEC814F5B1B%40solidlinks.nl > <https://groups.google.com/d/msgid/django-developers/0D5D730A-3C3E-4886-8C9C-3FEC814F5B1B%40solidlinks.nl?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Cheers, Brenton I host melbdjango <http://melbdjango.com>, it's rad! https://brntn.me // @sesh <https://twitter.com/sesh> -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAC_Rtmtx93JxxCvxHXvb841%2BLGD67i6AAvkWxzmAK_S-H3zdhg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
