Richard Steenbergen
|
| Posted: 11/24/2005, 12:31 PM |
|
Every project I have to go hack the Common files and add support for storing the passwords as a one-way hash ala crypt(). The check should be simple to implement as a security option, and the crypt() on the password field should be simple to implement as an action.
|
|
|
 |
ziggetty
Posts: 20
|
| Posted: 11/25/2005, 3:47 AM |
|
this is asked for again and again ( i think from the early beginning)
probably 80+ % of developers is doing this.
i would also vote for an voting system for wishes in this forum, so it is immediate clear which wishes are on the consideration list and how high they are valued by the user base.
|
 |
|
Graham Pearson
|
| Posted: 11/30/2005, 3:07 AM |
|
I do this but instead of modifying the common files, I modify my user
record page with custom code right before the Before Insert, Before
Update to crypt the password before writing to the database.
Richard Steenbergen wrote:
> Every project I have to go hack the Common files and add support for storing the
> passwords as a one-way hash ala crypt(). The check should be simple to implement
> as a security option, and the crypt() on the password field should be simple to
> implement as an action.
> ---------------------------------------
> Sent from YesSoftware forum
> http://forums.codecharge.com/
>
|
|
|
|
|
