Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7762457
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 1, 20262026-06-01T14:24:30+00:00 2026-06-01T14:24:30+00:00

I have a django auth_user table, and for some reason, some of the passcodes

  • 0

I have a django auth_user table, and for some reason, some of the passcodes are stores as sha1$... and others pbkdf2_sha256$.... I don’t see any rhyme or reason to it — what is the difference between these two and why would some be stored as one version, but others as another?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-01T14:24:32+00:00Added an answer on June 1, 2026 at 2:24 pm

    Did you perhaps upgrade from Django 1.3 to Django 1.4 while retaining user data? Django 1.4 introduced the newer, more secure hash for password storage, but should still be backwards-compatible with the old hashes as far as I am aware.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a django project, but for some reason basic jquery isn't working. <html>
I have a Django-created tables in PostgreSQL 8.4 database, where one table extends another.
I have a form like so: from django import forms from django.contrib.auth.models import User
I have a django server that serves the basic site with user, auth etc
Basically, I currently have login/ in urls.py redirect to the django.contrib.auth.views.login and that seems
I have Django running in Apache via mod_wsgi. I believe Django is caching my
I have django model which consist of parent child relationship filed I want to
i have django installed and seems to be working it worked page I want
I was trying to setup django . I do have Django-1.1-alpha-1. I was trying
Newbie question. I have Django models that look like this: class Video(models.Model): uploaded_by =

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.