[
https://issues.apache.org/jira/browse/QPID-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602969#action_12602969
]
Martin Ritchie commented on QPID-1058:
--------------------------------------
The concern with that solution was the reduced key space but given that the MD5
isn't exactly secure then this approach would at least allow us to have a
working SASL mechanism that will work with non-java languages.
While this is not ideal users do not have to use it if they are concerned about
the security implications.
We should really try and get Kevin Smith to provide us documentation on how the
SSL work he did works as this would allow us to secure a standard PLAIN
authentication.
> Add support for CRAM-MD5-HASHED as used by Java Broker
> ------------------------------------------------------
>
> Key: QPID-1058
> URL: https://issues.apache.org/jira/browse/QPID-1058
> Project: Qpid
> Issue Type: New Feature
> Components: Dot Net Client
> Affects Versions: M2, M2.1
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
> Fix For: M3
>
>
> Summary:
> As shown on the Qpid Interoperability page the .Net does not currently
> support the CRAM-MD5-HASHED SASL mechanism offered by the Java broker.
> http://cwiki.apache.org/confluence/display/qpid/Qpid+Interoperability+Documentation
> For the .Net client to interoperate with the Java broker using the Base64
> encoded MD5Hashed password file the .Net client needs to support this
> mechanism.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
