You should be able to define the encrypt method on your user model.
Here's the default:
# Encrypts some data with the salt.
def encrypt(password, salt)
Digest::SHA1.hexdigest("--#{salt}--#{password}--")
end
Bryan
On 10-06-17 10:51 AM, polarapfel wrote:
Hi everybody,
what is the most intelligent way to override the way the Hobo user
model encrypts passwords when persisting them in the database? By
default it uses SHA1 to create a hashed password. Actually I would
rather need passwords as hashed by the UNIX crypt(1) utility. So, how
do I change SHA1 in Hobo to crypt(1)? I know it's much less secure but
I'm dealing with a legacy system here. We might change to SHA1, but
not right now.
thanks,
Tobias W.
--
You received this message because you are subscribed to the Google Groups "Hobo
Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/hobousers?hl=en.
