[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: The objects...
Well it turns out that MySQL's encryption is very simular to crypt().
If PHP can't encrypt the password natively, then we should probably switch
to crypt. Just let me know before anyone starts making changes on this
because it WILL break my mod_perl http-auth module. It's pretty easy to
fix (I just need to back out of my hacks) but people are going to find
themselves locked out.
Also, realize there is no way to recover the existing passwords to convert
them to crypt(). We're going to have to redo them all.
On Sat, 30 Oct 1999, Micah K Yoder wrote:
> Spencer Portee wrote:
>
> > It can use crypt(5)(?) or it's own idiotic encryption. Use crypt.. it'll
> > be nicer.
>
> It's currently using MySQL encryption. Switching to crypt() is an
> option. What do you think people??? Only problem is crypt() is limited
> to 8 significant characters (I think). Perhaps md5() could be used...
>
--
Aaron Turner, Core Developer http://vodka.linuxkb.org/~aturner/
Linux Knowledge Base Organization http://linuxkb.org/
Because world domination requires quality open documentation.