[jira] Commented: (JAMES-332) SHA hard coded in adduser

["Brill Pappin (JIRA)" <se...@james.apache.org>]

     [ http://nagoya.apache.org/jira/browse/JAMES-332?page=comments#action_55165 ]
     
Brill Pappin commented on JAMES-332:
------------------------------------

Sorry, miss-typed that, I meant SHA is the default digest.

> SHA hard coded in adduser
> -------------------------
>
>          Key: JAMES-332
>          URL: http://nagoya.apache.org/jira/browse/JAMES-332
>      Project: James
>         Type: Bug
>   Components: SpoolManager & Processors, UsersStore & UsersRepository
>     Versions: 2.2.0
>  Environment: FreeBSD, Sun JDK 1.4.2-p6, MySQL via. C-JDBC.
>     Reporter: Brill Pappin
>     Priority: Critical

>
> It seems that JDBC is the default digest alg when creating users. this works fine when the use repository doesn't have to work with anything else, but MD5 is more common.
> In my case, I'm using a custom configuration that allows me to use the same auth table for Tomcat and James. I think (though I haven't checked) that I can configure tomcat to use SHA, but I have a significan't amount of legacy data that uses MD5, whic is going to break thing.
> As of now, my only option is to *try* and recompile James with MD5 as the default (and I havn't had much luck yet). Because of that, this ticket is marked as Critical.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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