[
https://issues.apache.org/jira/browse/QPID-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755686#action_12755686
]
Ken Giusti commented on QPID-1899:
----------------------------------
update: my assumption that:
[kgiu...@localhost cpp]$ src/tests/.libs/lt-perftest -b localhost.localdomain
--mechanism GSSAPI --username testuser --tx 1 --count 1 --port 5672 --summary
was not encrypted is *False*: GSSAPI is providing encryption in this example
(max-ssf = 256). Therefore this particular "issue" is not-a-bug.
The second issue:
[kgiu...@localhost cpp]$ src/tests/.libs/lt-perftest -b localhost.localdomain
--mechanism GSSAPI --username testuser --tx 1 --count 1 --port 5671 -P ssl
--summary
2009-09-15 10:55:12 warning Connection closed
Connection closed
appears to be a legitimate bug. I'll work on fixing this as part of the
"clean" fix implementation.
> --require-encryption doesn't work unless cyrus sasl authentication is turned
> on
> -------------------------------------------------------------------------------
>
> Key: QPID-1899
> URL: https://issues.apache.org/jira/browse/QPID-1899
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: 0.5
> Reporter: Gordon Sim
> Assignee: Gordon Sim
> Fix For: 0.6
>
> Attachments: qpid-1899-hacky.patch
>
>
> If you specify --require-encryption and --auth no then the broker will allow
> un-encrypted conections. (If on the other hand you have authentication on, it
> will prevent you connecting with anything other than a mech that supports
> encryption and will require an encrypting sasl security layer - or of course
> an ssl connection)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
