> > But, to be consistent with Django 1.x going forward, let's define 36,000 > iterations as "acceptable performance" for a Python2 with Django 1.11 > install on a typical piece of server hardware today (beginning of 2017). A > useful benchmark would be to determine how many iterations would yield the > same delay on a Py3 + Django 1.11 install on the same server. >
That sounds like a sensible benchmark to see where we are at current. I think Django should be aiming for 100k+ as default at least to match the Python docs though. Let's not forget that users can tweak it down as well as up if they do have problems with the execution time. On 3 January 2017 at 17:16, Martin Koistinen <mkoisti...@gmail.com> wrote: > I think the best practice is to set the iterations as high as you can > tolerate without adversely affecting the user experience as they log-in. > Iteration numbers as high as 200,000 for SHA-256 or even more are not > unheard of these days. Without looking at an application's password > expiration policies, there's really no "one size fits all" number here. > > But, to be consistent with Django 1.x going forward, let's define 36,000 > iterations as "acceptable performance" for a Python2 with Django 1.11 > install on a typical piece of server hardware today (beginning of 2017). A > useful benchmark would be to determine how many iterations would yield the > same delay on a Py3 + Django 1.11 install on the same server. > > This should probably server as a *baseline* default number of iterations > and, IMHO, there should probably be reasonable amount of encouragement in > the documentation to set the number of iterations to a value as high as the > application can tolerate. Ideally, there could be some in-built > benchmarking tools to make this easier for the admin. > > > On Monday, January 2, 2017 at 9:50:26 AM UTC-5, Tim Graham wrote: >> >> Now that Python 2 is dropped in Django 2.0 and a faster implementation of >> pbkdf2 is guaranteed to be available (from what I understand), it's time to >> reevaluate our strategy for increasing the number of iterations each >> release. >> >> I'm not sure how to evaluate potential performance issues from bumping >> the number of iterations too aggressively. I'd be happy to do some >> benchmarks but I'm not sure what will be meaningful. >> >> The Python docs say, "As of 2013, at least 100,000 iterations of SHA-256 >> are suggested." [0] >> >> Here are the number of iterations in recent versions of Django: >> Django 1.8: 20000 >> Django 1.9: 24000 >> Django 1.10: 30000 >> Django 1.11: 36000 >> >> [0] https://docs.python.org/3/library/hashlib.html#hashlib.pbkdf2_hmac >> >> On Tuesday, September 22, 2015 at 5:15:37 PM UTC-4, Aymeric Augustin >> wrote: >>> >>> On 22 sept. 2015, at 21:21, Tim Graham <timog...@gmail.com> wrote: >>> >>> > At this point, I'm inclined to continue with the 20-25% iterations >>> increase per release methodology we've been using unless someone wants to >>> advocate for one of the other proposals. >>> >>> >>> I agree. >>> >>> -- >>> Aymeric. >>> >>> >>> >>> -- > 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 django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > 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/583ae294-7307-4db2-898a- > 7f6e558df904%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/583ae294-7307-4db2-898a-7f6e558df904%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Adam -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. 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/CAMyDDM2vWvQL%3Dj8Q6Z-sLoRHNsZCcHKSa1fH%2BWq7aSn_E9MgcA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
