Take a look at https://docs.djangoproject.com/en/stable/topics/auth/passwords/#password-upgrading-without-requiring-a-login
Instead of SHA1PasswordHasher().encode() you'll want to use vBulletin's hashing algorithm. On Tuesday, March 15, 2016 at 11:54:32 AM UTC-4, jorr...@gmail.com wrote: > > I'm converting an old vBulletin 3.8 installation to a Django web app and > I'm wondering if I can migrate users over with their passwords intact. > > vBulletin uses *md5(md5(password) + salt)* to hash its passwords, would > any of Django's built-in password hashers work with this out of the box? > > Some of the salts also contain the *$* character, I'm guessing that's a > big problem? > > I'm wondering if it would be easiest (or even possible) to write a custom > password hasher for this or just have everyone reset their passwords once > the new site goes live. > > Any thoughts on this would be appreciated! > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/e46b3bc7-b6ec-4654-ad4d-c0345d56278e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
