[
https://issues.apache.org/jira/browse/QPID-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti resolved QPID-4744.
------------------------------
Resolution: Fixed
The commit:
http://svn.apache.org/viewvc?view=revision&revision=1468683
> qpid-tool does not allow separate keyfile for SSL connections
> -------------------------------------------------------------
>
> Key: QPID-4744
> URL: https://issues.apache.org/jira/browse/QPID-4744
> Project: Qpid
> Issue Type: Bug
> Components: Python Tools
> Affects Versions: 0.20
> Reporter: Ken Giusti
> Assignee: Ken Giusti
> Priority: Trivial
> Fix For: 0.23
>
>
> All qpid tools support client-side authentication. This is provided by two
> options to each command: --ssl-certificate and --ssl-keyfile. The
> --ssl-certificate option specifies the client side certificate file (in PEM
> format). If the certificate file does NOT contain the encrypted private key,
> then the --ssl-keyfile must be specified. It provides for a separate file
> containing the encrypted private key (in PEM format).
> qpid-tool does not support the separate keyfile option.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
