[ https://issues.apache.org/jira/browse/QPID-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762198#action_12762198 ]
Gordon Sim commented on QPID-1899: ---------------------------------- I like this approach. As compared with the earlier alteration of the OutputControl interface, this change doesn't leak into unrelated areas of the code. One question though; altering the min_ssf in the SaslAuthenticator makes perfect sense, but whats the motivation behind altering the max_ssf? > --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, > qpid-1899.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