[
https://issues.apache.org/jira/browse/DISPATCH-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953751#comment-14953751
]
ASF GitHub Bot commented on DISPATCH-181:
-----------------------------------------
GitHub user ganeshmurthy opened a pull request:
https://github.com/apache/qpid-dispatch/pull/17
DISPATCH-181 - Removed password field from the ssl_attributes array s…
…o that the ssl->enabled will not be set to true
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ganeshmurthy/qpid-dispatch DISPATCH-181
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/qpid-dispatch/pull/17.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #17
----
commit 7a2ef9f9704ada94502c603abe85fc2fa571336e
Author: ganeshmurthy <[email protected]>
Date: 2015-10-12T21:16:42Z
DISPATCH-181 - Removed password field from the ssl_attributes array so that
the ssl->enabled will not be set to true
----
> ssl_enabled flag on the config set to true if "password" is one of the fields
> in the config file
> ------------------------------------------------------------------------------------------------
>
> Key: DISPATCH-181
> URL: https://issues.apache.org/jira/browse/DISPATCH-181
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node
> Affects Versions: 0.5
> Reporter: Ganesh Murthy
>
> The config->ssl_enabled is set to true if any of the following attributes are
> present in the qdrouterd config file (qdrouterd.conf)
> "certDb", "certFile", "keyFile", "passwordFile", "password"
> I introduced two fields (user name and password) in qdrouter.json file and
> because of the above code the config->ssl_enabled is always set to true and
> the underlying proton API always tries to do an SSL handshake.
> The "password" field should be removed from the above list
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
