1 Aug 2010 01:06
Re: salted passwords
Leonardo Rodrigues <leolistas <at> solutti.com.br>
2010-07-31 23:06:52 GMT
2010-07-31 23:06:52 GMT
Em 31/07/2010 18:51, Patrick Westenberg escreveu:
> Leonardo Rodrigues schrieb:
>>
>> that's all because i already have a account manager system,
>> written on PHP, which i had to kept. So i was trying to understand
>> how that's work to make it work on my system i couldnt stop using.
>>
>> but after some tryings i got everything running. All my passwords
>> were already migrated from plaintext to Salted-SHA2-256.
>
> Hi Leonardo,
>
> can you tell me how you solved your problem with creating salted
> passwords via PHP?
>
Hi .... yes i've acchieved some PHP routines for creating the
salted SHA256 password with random salt and also comparing a stored
hashed password with a plaintext supplied one.
encoded passwords will be exited as:
{SSHA256.HEX}acf5ce0f51cca2077e27884a7cec385c430bb402c2f961b02bfa779c18aaf9a373772d99
encoded password strings is 85-char length with the SSHA.256 prefix and
72 without it
as i'm storing passwords with the SSHA256.HEX prefix, my dovecot
conf has:
(Continue reading)
But, it doesn't work:
ldap.conf:
user_attrs = postalAddress=domain,homeDirectory=/imap/spool/%d/%1n/%n
user_filter = (&(objectClass=posixAccount)(uid=%n))
pass_attrs = postalAddress=domain, uid=user, userPassword=password
pass_filter = (&(objectClass=posixAccount)(uid=%n))
After login, DoveCot creates the directory /imap/spool/f/foo, instead
of /imap/spool/subdomain.domain.bla/f/foo
Log (anonymized) :
RSS Feed