You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Norman Maurer (JIRA)" <se...@james.apache.org> on 2010/02/09 21:41:28 UTC
[jira] Assigned: (JAMES-332) Support other digest algorithm (was:
SHA hard coded in adduser)
[ https://issues.apache.org/jira/browse/JAMES-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Norman Maurer reassigned JAMES-332:
-----------------------------------
Assignee: Norman Maurer
> Support other digest algorithm (was: SHA hard coded in adduser)
> ---------------------------------------------------------------
>
> Key: JAMES-332
> URL: https://issues.apache.org/jira/browse/JAMES-332
> Project: JAMES Server
> Issue Type: Improvement
> Components: SpoolManager & Processors, UsersStore & UsersRepository
> Affects Versions: 2.2.0
> Environment: FreeBSD, Sun JDK 1.4.2-p6, MySQL via. C-JDBC.
> Reporter: Brill Pappin
> Assignee: Norman Maurer
> Priority: Minor
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org