Two comments: (1) The documentation says: *By default, no validation is performed and all passwords are accepted.* So they are not enabled by default in new projects. (2) There is one recommendation that we are not following: *No composition rules.* There's a validator to forbid numeric-only passwords, but adding non-numeric characters is *illusory complexity*, I think. Computers have as hard time to guess alpha-characters as it has to guess digits. It's all bytes to the computer. To the attacker, they will have to test alpha-characters and digits alike, since they don't know if the password is numeric-only. Now, I'm not saying we should follow this, just that we are not, and that's ok. I guess numeric passwords will be easier to guess if the attacker is someone who could see you type your password from a distance and, since you'll only use numbers, that's the hint they need to make their job easier.
On Wed, Nov 23, 2016 at 1:03 PM, 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. > -- 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/CAO_YKa1VXK2oQ8-anH6W2X2wHat2bMj7bgKor7WBanBnJtw2bQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
