Hide Forgot
Description of problem: When using qpid-send/qpid-receive clients for sending/receiving message to default broker address and the ssl transport is requested by the client, the client is successful even when connecting to non-ssl broker: qpid-send --connection-options "{transport: 'ssl'}" -a "q;{create:always}" Note: When the broker address is specified for the connection then the connection is not initiated (as expected): qpid-send --connection-options "{transport: 'ssl'}" -a "q;{create:always}" -b localhost qpid-send: Unknown protocol: ssl (/builddir/build/BUILD/qpid-0.22/cpp/src/qpid/client/Connector.cpp:52) Version-Release number of selected component (if applicable): qpid-cpp-*-0.22-14 How reproducible: 100% Steps to Reproduce: 1. run a non-ssl broker 2. qpid-send --connection-options "{transport: 'ssl'}" -a "q;{create:always}" 3. qpid-config queues 4. the queue q was created Actual results: ssl connection to non-ssl broker succeeds Expected results: ssl connection to non-ssl broker is aborted Additional info:
Fixed upstream: https://svn.apache.org/r1524506
Tested on RHEL6.5 (both i386 and x86_64). This issue has been fixed. Packages used for testing: python-qpid-0.22-9.el6 python-qpid-qmf-0.22-25.el6 qpid-cpp-client-0.22-30.el6 qpid-cpp-client-devel-0.22-30.el6 qpid-cpp-client-devel-docs-0.22-30.el6 qpid-cpp-client-ssl-0.22-30.el6 qpid-cpp-server-0.22-30.el6 qpid-cpp-server-devel-0.22-30.el6 qpid-cpp-server-linearstore-0.22-30.el6 qpid-cpp-server-ssl-0.22-30.el6 qpid-cpp-server-xml-0.22-30.el6 qpid-java-client-0.22-5.el6 qpid-java-common-0.22-5.el6 qpid-java-example-0.22-5.el6 qpid-jca-0.22-1.el6 qpid-jca-xarecovery-0.22-1.el6 qpid-proton-c-0.6-1.el6 qpid-qmf-0.22-25.el6 qpid-snmpd-1.0.0-15.el6 qpid-tools-0.22-7.el6 -> VERIFIED
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2014-1296.html