[
https://issues.apache.org/jira/browse/DERBY-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041544#comment-13041544
]
Siddharth Srivastava commented on DERBY-4795:
---------------------------------------------
Hi
I too think a usage error would be appropriate as if some sort of default is
there then either we'll have to show a message that which sslmode has been used
and user may not comply with that.
If we go with the usage error, in my opinion following error would be
appropriate:
Error <Error Id>: Missing <sslmode> argument
Usage: -ssl <sslmode>
SSLMODE can be any of the following:
SSL_OFF: Turns off SSL. No SSL encryption would
be used
SSL_BASIC: Use basic SSL Encryption
SSL_PEER_AUTHENTICATION: Use SSL Encryption with Peer Authentication
I am not very sure about the error id (is it possible to generate an error id ?
)
Please share your opinion.
> Starting network server with -ssl turns SSL off
> -----------------------------------------------
>
> Key: DERBY-4795
> URL: https://issues.apache.org/jira/browse/DERBY-4795
> Project: Derby
> Issue Type: Bug
> Components: Network Server
> Affects Versions: 10.6.1.0
> Reporter: Knut Anders Hatlen
> Assignee: Siddharth Srivastava
> Labels: derby_triage10_8
>
> If you start the network server with the -ssl option and no <sslmode>
> argument, the server will be started in plain text mode.
> For example:
> java -jar derbynet.jar start -ssl
> If -ssl is specified without <sslmode>, I would have expected that SSL was
> enabled (not sure which SSL mode, basic or peerAuthentication, is more
> appropriate) or that the command failed because of the missing argument.
> Treating "-ssl" as an alias for "-ssl off" sounds unintuitive to me.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
