Am going to post the few comments I have this afternoon.
On 9/8/06, Mike Matrigali (JIRA) <derby-dev@db.apache.org> wrote:
>
> [ http://issues.apache.org/jira/browse/DERBY-1675?page=all ]
>
> Mike Matrigali updated DERBY-1675:
> ----------------------------------
>
>
> francois do you have any initial comments on the change? tests passed for
> me and they look reasonable but would prefer to get review of someone
> experienced in this code. I can work on committing this today or tommorow,
> but after that I will be away for a week. This seems like something that
> would be nice to get into 10.2.
>
> > 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.1.3.1, 10.1.3.0, 10.1.2.1, 10.1.1.0, 10.0.2.1,
> 10.0.2.0, 10.2.1.0
> > 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
>
>
>
|