[ http://issues.apache.org/jira/browse/JAMES-334?page=comments#action_12318341 ]
Brill Pappin commented on JAMES-334: ------------------------------------ The problem was that I had to modify James to use the same authentication store as several other applications, and because the alg was so "strange" it caused a real problem. I don't think that the one it was using was all that bad, but it was very tough to change. I'd request, at the very least you allow the administrator to specify the method to use... and idealy provide a way for someone to write a custome auth module. > SHA hash incompatable with common generation methods > ---------------------------------------------------- > > Key: JAMES-334 > URL: http://issues.apache.org/jira/browse/JAMES-334 > Project: James > Type: Bug > Components: UsersStore & UsersRepository > Versions: 2.2.0 > Environment: FreeBSD, JDK 1.4.2, MySQL via. C-JDBC > Reporter: Brill Pappin > Priority: Minor > > This ticket is related to: JAMES-332 > It appears the SHA password hash is not compatable with all other methods of > generating an SHA hash I've tried. For example: > SELECT SHA("test") in MySQL > a94a8fe5ccb19ba61c4c0873d391e987982fbbd3 > generates what I'd expect, however: > the remote manager tool sets: > CY9rzUYh03PK3k6DJie0 > which doesn't even "look" like SHA. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
