[ http://issues.apache.org/jira/browse/DERBY-1675?page=comments#action_12433537 ] Sunitha Kambhampati commented on DERBY-1675: --------------------------------------------
Thanks Francois for your comments. > "We're loosing the returned list to check here" Wrt to #2, We are not losing the returned list to check since the readSecMecAndSECCHKCD method prints the secmec that it receives. Actually that was the reason, I had to print the values in readSecMecAndSECCHKCD. Thus we have two different cannons, which is why the testProtocol.out was added for ibm14. So if you look at the diff for testProtocol.out , for e.g., you will see this. ...... Test trying security mechanism we don't support +SECMEC=3 SECMEC=4 SECMEC=8 SECCHKCD=1 In case for ibm142 (new masterfile that got added), you would see +Test trying security mechanism we don't support +SECMEC=3 SECMEC=9 SECMEC=4 SECMEC=8 SECCHKCD=1 Do you agree ? or am I missing something in your comment. I like your suggestion for the comments in the code. I'll make that change. Thanks. > Network Server should not send to client that it supports EUSRIDPWD when > running against Sun JVM > ------------------------------------------------------------------------------------------------ > > Key: DERBY-1675 > URL: http://issues.apache.org/jira/browse/DERBY-1675 > Project: Derby > Issue Type: Improvement > Components: Network Server > Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.2.1.0, 10.1.2.1, > 10.1.3.0, 10.1.3.1 > Reporter: Sunitha Kambhampati > Assigned To: Sunitha Kambhampati > Priority: Minor > Attachments: derby1675.diff.txt, derby1675.stat.txt > > > As part of ACCSECRD, if the server does not accept the security mechanism > sent by the client, the server will send a list of security mechanism that > it supports. Currently even when the server is running with sun jvm, it will > still send EUSRIDPWD as a sec mec that it supports, which is incorrect. The > server should test if it can support EUSRIDPWD dynamically and if it does, > only then send EURRIDPWD as an option that it supports. > see DRDAConnThread.writeACCSECRD(int) -- 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
