[
https://issues.apache.org/jira/browse/DERBY-4483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851493#action_12851493
]
Knut Anders Hatlen commented on DERBY-4483:
-------------------------------------------
To make it easier to choose another algorithm than the default, we may want to
handle derby.authentication.builtin.algorithm more like
derby.database.sqlAuthorization during database creation. If
d.d.sqlAuthorization is set as a system property when a database is created,
its value will be persisted in the database. This way it will be possible to
change the algorithm at database creation time without executing any SQL
statements.
> Provide a way to change the hash algorithm used by BUILTIN authentication
> -------------------------------------------------------------------------
>
> Key: DERBY-4483
> URL: https://issues.apache.org/jira/browse/DERBY-4483
> Project: Derby
> Issue Type: Improvement
> Components: Services
> Affects Versions: 10.5.3.0
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Priority: Minor
> Fix For: 10.6.0.0
>
> Attachments: comments.diff, derby-4483-1a.diff, derby-4483-1a.stat,
> derby-4483-2a.diff, derby-4483-2a.stat, errormsg.diff, experiment.diff,
> releaseNote.html, releaseNote.html, toHexByte.diff, upgrade-test.diff
>
>
> The BUILTIN authentication scheme protects the passwords by hashing them with
> the SHA-1 algorithm. It would be nice to have way to specify a different
> algorithm so that users can take advantage of new, stronger algorithms
> provided by their JCE provider if so desired.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
