qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPIDJMS-150) Scram SHA SASL support for authentication
Date Mon, 22 Feb 2016 17:06:18 GMT

    [ https://issues.apache.org/jira/browse/QPIDJMS-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157283#comment-15157283

ASF subversion and git services commented on QPIDJMS-150:

Commit 36469f1c7b2a8dcc3c773fd0316e952b7bab8472 in qpid-jms's branch refs/heads/master from
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=36469f1 ]

QPIDJMS-150: Add support for SASL SCRAM SHA1/256 [RFC-5802/7677]

* Include unit tests based on known good test data from their respective 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

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message