You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Sunitha Kambhampati (JIRA)" <de...@db.apache.org> on 2006/09/08 19:45:24 UTC
[jira] Resolved: (DERBY-1756) Revert change in client that defaults
the secmec to eusridpwd.
[ http://issues.apache.org/jira/browse/DERBY-1756?page=all ]
Sunitha Kambhampati resolved DERBY-1756.
----------------------------------------
Resolution: Fixed
Derby Info: [Regression] (was: [Patch Available, Regression])
This fix was merged to 10.2 as part of the mega merge: http://svn.apache.org/viewvc?view=rev&revision=441540
Thanks to Rick and Mike for the commits.
I have verified that the fix is in trunk and 10.2 and have successfully run the testSecMec test.
> Revert change in client that defaults the secmec to eusridpwd.
> --------------------------------------------------------------
>
> Key: DERBY-1756
> URL: http://issues.apache.org/jira/browse/DERBY-1756
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.2.1.0, 10.3.0.0
> Reporter: Sunitha Kambhampati
> Assigned To: Sunitha Kambhampati
> Fix For: 10.2.1.0, 10.3.0.0
>
> Attachments: Derby1756.2.diff.txt, derby1756.diff.txt, derby1756.stat.txt
>
>
> With changes to derby-962, the client would default to eusridpwd if the client jvm supports it. It is not sufficient to only check if client jvm can support eusridpwd but we need to verify if the server can support the particular secmec.
> There are other existing jiras DERBY-1675,DERBY-1517,DERBY-1755 that will help to address the issue of upgrading to a better security mechanism.
> This jira will change the default security mechanism to 3 as it was before derby-962 changes.
--
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