I wrote a quick off-list reply to this last night, but thought it
might be worth pointing out parts of it publicly as well so anyone who
searches the archives with similar problems will spot this:
1. Django does still support plain old unsalted md5 passwords for
login (for backwards compatibility
> The original poster suggested adding a field called password_md5 to a
> model that is an extension of User. It was never indicated that such a
> field already existed.
Ah, my bad. I misinterpreted.
--~--~-~--~~~---~--~~
You received this message because you are
On Thu, 2007-06-28 at 05:37 +, Bryan Veloso wrote:
> Alright. I tried looking in the actual source for any mention of
> password_md5... and it no longer exists.
The original poster suggested adding a field called password_md5 to a
model that is an extension of User. It was never indicated tha
Alright. I tried looking in the actual source for any mention of
password_md5... and it no longer exists. So I'm sure I just can't call
the field. I'd have to recreate it or something correct?
--~--~-~--~~~---~--~~
You received this message because you are subscri
> The usual route I go with when trying to extend on the User model is
> to create a new model and link it to the User model. For example:
>
> class UserExt(models.Model):
> user = models.ForeignKey(User)
> # ... other fields that you need here
>
> def __init__(self, user):
> s
On 6/27/07, Bryan Veloso <[EMAIL PROTECTED]> wrote:
> At the moment, the game can only read md5 or plain-text passwords, and
> I know that Django has the hash$salt$hash (or something. :P) way of
> doing it. So I can't just copy the password from the User model to the
> account table since the game
Alright, I did about 2 hours of searching today and I'm beginning to
think that the above is an impossibility. Which probably means that
I'm going to have to bypass Django authentication and make my own, but
I don't even know where to start on that, so I'm at quite a loss. :/
--~--~-~--~
Long story short, I'm building a control panel + backend to an MMORPG.
It runs off of a mySQL database, I used inspectdb, and all of that
worked perfectly. However, now I have some duplicate data, the User
model (since I'm using django-registration) and the account table of
the inspected database.
8 matches
Mail list logo
