[
https://issues.apache.org/jira/browse/DERBY-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475158
]
Bernt M. Johnsen commented on DERBY-2356:
-----------------------------------------
Thanks John!
1) You need -ssl basic on these too, since they are clients. My mistake, it's
not mentioned in the func spec, but it is implemented. This is also another
argument for DERBY-2362.
3) This is in line with the other options, e.g.
java -jar derbyrun.jar server start p=1234
Invalid number of arguments for command start.
or
java -jar derbyrun.jar server start -p=1234
Argument -p=1234 is unknown.
4) I will clarify this
5) Typo. I will fix them (some are already fixed in my sandbox)
> Make SSL server authentication optional
> ---------------------------------------
>
> Key: DERBY-2356
> URL: https://issues.apache.org/jira/browse/DERBY-2356
> Project: Derby
> Issue Type: Improvement
> Components: Network Client, Network Server
> Affects Versions: 10.3.0.0
> Reporter: Bernt M. Johnsen
> Assigned To: Bernt M. Johnsen
> Fix For: 10.3.0.0
>
> Attachments: derby-2356-v1.diff, derby-2356-v1.stat, SSLFuncSpect.txt
>
>
> Default SSL behaviour is to require serer authentication. For a database
> application this is not as important as it is for web browsers and also
> creates som extra hassle for the user/application programmer. Since the main
> objective for SSL in Derby is encryption on the wire, server authentication
> should be optional (the same way client authentication is).
> This also creates some symmetry which can be exploited to simplify the user
> interfce somewhat. This improvement to DERBY-2108 is described in the
> attached functional specification. See the attachment for details.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
