[
https://issues.apache.org/jira/browse/QPID-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756692#action_12756692
]
Ken Giusti commented on QPID-1899:
----------------------------------
The SSF_EXTERNAL stuff doesn't appear to buy us anything: doing a sasl_getopts(
SASL_SFF ) reports a negotiated ssf of zero, even if I set it to non-zero via
sasl_setopts( SASL_SFF_EXTERNAL). The client (perftest) logs that there is no
security layer regardless, also:
2009-09-17 14:45:30 debug No security layer in place
So I don't see an advantage with the EXTERNAL stuff. I'm fine with the current
patch - let's go with that.
> --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-9-17.patch, 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
