[ http://issues.apache.org/jira/browse/DERBY-1756?page=comments#action_12432205 ] Sunitha Kambhampati commented on DERBY-1756: --------------------------------------------
Rereading my previous comment, I think I wasnt very clear. (sorry). so reposting my comment. The only change in the derby1756.2.diff.txt patch from the previous patch is to leave the code for eusridpwd check commented out in getUpgradedSecurityMechanism() with a comment referring to DERBY-1755 and DERBY-1517. Since no other functional changes went in this version of the patch , I have not run derbyall. I ran the testSecMec.java test against ibm142/ibm15 and jdk142 with DerbyNetClient OK on windows. Can someone please review and commit this patch. Thanks. > 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 > Reporter: Sunitha Kambhampati > Assigned To: Sunitha Kambhampati > Fix For: 10.2.1.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
