sentry 6.4.4 does not store password in bcrypt anymore

[kzw]

This is despite what the documentation says

http://sentry.readthedocs.org/en/latest/quickstart/index.html#additional-utilities

Is this the case of the documentation being out-of date?

If password hash was indeed changed, this will make it hard to migrate the user-database.

[dcramer]

Django should be defaulted to bcrypt/it's equiv but I will double check. 

That said Sentry never natively used bcrypt. We ran a custom hasher for a while to do this on getsentry.com

On Thu, Feb 20, 2014 at 10:14 AM, k z notifications@github.com wrote:

This is despite what the documentation says
http://sentry.readthedocs.org/en/latest/quickstart/index.html#additional-utilities
Is this the case of the documentation being out-of date?

If password hash was indeed changed, this will make it hard to migrate the user-database.

Reply to this email directly or view it on GitHub:
#1123

[kzw]

We were using 6.3.2 and we made it use bcrypt by having 'django_bcrypt' in INSTALLED_APPS

With the same config file 6.4.4 does not respect this anymore. Perhaps this is django fault. Thanks for looking.

[dcramer]

Ah, we actually should update the documentation either way.

Django 1.5+ should have better defaults so it’s not longer something needed. That said, here’s what we had to do at the time of:

http://justcramer.com/2013/05/07/making-django-1-dot-5-compatible-with-django-bcrypt/

On Thursday, February 20, 2014 at 10:59 AM, k z wrote:

We were using 6.3.2 and we made it use bcrypt by having 'django_bcrypt' in INSTALLED_APPS
With the same config file 6.4.4 does not respect this anymore. Perhaps this is django fault. Thanks for looking.

—
Reply to this email directly or view it on GitHub (#1123 (comment)).

[kzw]

thanks. I had already asked my users to recreate their accounts.