james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ahmet Kaplan (JIRA)" <server-...@james.apache.org>
Subject [jira] [Created] (JAMES-1677) Upgrade the users hashing algorithm type
Date Thu, 28 Jan 2016 19:44:39 GMT
Ahmet Kaplan created JAMES-1677:

             Summary: Upgrade the users hashing algorithm type
                 Key: JAMES-1677
                 URL: https://issues.apache.org/jira/browse/JAMES-1677
             Project: James Server
          Issue Type: Improvement
            Reporter: Ahmet Kaplan
            Priority: Minor

User data models use different hashing algorithms:
JPA           -> MD5
JDBC        -> SHA
Cassandra -> SHA1
HBase       -> MD5
Memory     -> MD5
JCR           -> MD5

There are lots of hashing discussions such as http://stackoverflow.com/questions/20186354/best-practice-of-hashing-passwords/20186472#20186472

I offer SHA-256 for all user data models. 

P.S: Not exactly related but Google Chrome does not allow SHA1 at next year.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message