[
https://issues.apache.org/jira/browse/DERBY-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476916
]
Daniel John Debrunner commented on DERBY-2363:
----------------------------------------------
bernt> To make a good implementation for this approach, these admin commands
should be split out from NetworkServerControlImpl into a separate class or
package (which is wise anyway, since these commands are clients and not really
very much related to the server).
+1
In looking at the network startup code (DERBY-1966) it struck me that the
NetworkServerControlImpl class is overly complex due to the mixing of client
commands and the actual logic to run a network server. Such a split should
probably stop using the name NetworkServerControlImpl and instead two classes
with names that reflect their purpose, commands and server.
> Add initial handshake on connection setup to determine server's required ssl
> support level and avoid client side attribute settings.
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2363
> URL: https://issues.apache.org/jira/browse/DERBY-2363
> Project: Derby
> Issue Type: Improvement
> Components: Network Client, Network Server, Security
> Reporter: Daniel John Debrunner
> Assigned To: Bernt M. Johnsen
> Fix For: 10.3.0.0
>
>
> Based upon some of the discussion in DERBY-2108, it would be useful to have
> some initial handshake between the client and the server to indicate the
> required level of ssl support. This would avoid client applications having to
> setup ssl related JDBC attributes or DataSource properties.
> Thus one could change the server to be ssl enabled without having to change
> any applications.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
