You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2016/02/21 18:47:18 UTC
[jira] [Comment Edited] (QPIDJMS-150) Scram SHA SASL support for
authentication
[ https://issues.apache.org/jira/browse/QPIDJMS-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15155777#comment-15155777 ]
Keith Wall edited comment on QPIDJMS-150 at 2/21/16 5:46 PM:
-------------------------------------------------------------
Thanks for the initial comments. I've added some unit tests based on known-good data taken from the RFCs. (edit: latest patch further improves test cases).
was (Author: k-wall):
Thanks for the initial comments. I've added some unit tests based on known-good data taken from the RFCs.
> Scram SHA SASL support for authentication
> -----------------------------------------
>
> Key: QPIDJMS-150
> URL: https://issues.apache.org/jira/browse/QPIDJMS-150
> Project: Qpid JMS
> Issue Type: Improvement
> Components: qpid-jms-client
> Reporter: Keith Wall
> Fix For: 0.9.0
>
> Attachments: 0001-QPIDJMS-150-Add-support-for-SASL-SCRAM-SHA1-256-RFC-.patch
>
>
> The SCRAM SHA-1 and 256 SASL mechanisms https://tools.ietf.org/html/rfc5802 offer better security than older SASL implementations. In particular the authentication information stored in the authentication database is not sufficient to impersonate the client if the database were to be stolen.
> (The Java Broker already supports these mechanisms. The intention is to switch to recommend SCRAM instead of CRAM-MD5 shortly. One barrier to making this switch is the absence of support in the client).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org