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 "Brill Pappin (JIRA)" <se...@james.apache.org> on 2004/11/05 04:05:32 UTC
[jira] Created: (JAMES-332) SHA hard coded in adduser
SHA hard coded in adduser
-------------------------
Key: JAMES-332
URL: http://nagoya.apache.org/jira/browse/JAMES-332
Project: James
Type: Bug
Components: UsersStore & UsersRepository, SpoolManager & Processors
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
[jira] Updated: (JAMES-332) Support other digest algorithm (was: SHA hard coded in adduser)
Posted by "Stefano Bagnara (JIRA)" <se...@james.apache.org>.
[ http://issues.apache.org/jira/browse/JAMES-332?page=all ]
Stefano Bagnara updated JAMES-332:
----------------------------------
Summary: Support other digest algorithm (was: SHA hard coded in adduser) (was: SHA hard coded in adduser)
type: Improvement (was: Bug)
Description:
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.
was:
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.
Priority: Minor (was: Critical)
Cleaning JIRA: This is not a BUG but a request for an improvement.
I changed the topic and I consider it to include the other related reports.
Please look at the descriptions in the already resolved issues linked to this issue.
> Support other digest algorithm (was: SHA hard coded in adduser)
> ---------------------------------------------------------------
>
> Key: JAMES-332
> URL: http://issues.apache.org/jira/browse/JAMES-332
> Project: James
> Type: Improvement
> Components: UsersStore & UsersRepository, SpoolManager & Processors
> Versions: 2.2.0
> Environment: FreeBSD, Sun JDK 1.4.2-p6, MySQL via. C-JDBC.
> Reporter: Brill Pappin
> 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.
-
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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Assigned: (JAMES-332) Support other digest algorithm (was:
SHA hard coded in adduser)
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ 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
[jira] Commented: (JAMES-332) SHA hard coded in adduser
Posted by "Brill Pappin (JIRA)" <se...@james.apache.org>.
[ http://nagoya.apache.org/jira/browse/JAMES-332?page=comments#action_55167 ]
Brill Pappin commented on JAMES-332:
------------------------------------
Another related password digest problem, see: JAMES-334
> 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
[jira] Commented: (JAMES-332) SHA hard coded in adduser
Posted by "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