You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2011/06/01 10:26:52 UTC

[jira] [Commented] (DERBY-4795) Starting network server with -ssl turns SSL off

    [ https://issues.apache.org/jira/browse/DERBY-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042040#comment-13042040 ] 

Knut Anders Hatlen commented on DERBY-4795:
-------------------------------------------

I don't think the "No command given" message or the extra usage information (it's printed twice) is intended. But the same thing happens if you use the -p or -h option with no value, so it looks like an existing problem and not something with your patch.

> 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
>         Attachments: d4795.diff
>
>
> 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