[jira] [Closed] (JAMES-332) Support other digest algorithm (was: SHA hard coded in adduser)

["Benoit Tellier (Jira)" <se...@james.apache.org>]

     [ https://issues.apache.org/jira/browse/JAMES-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benoit Tellier closed JAMES-332.
--------------------------------
    Resolution: Won't Fix

James 2.3 is unmaintained, end of life.

Feel free to reopen if work is planned on this.

> 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 was sent by Atlassian Jira
(v8.20.7#820007)

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