qpid-dev mailing list archives

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

     [ https://issues.apache.org/jira/browse/QPIDJMS-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robbie Gemmell resolved QPIDJMS-150.
------------------------------------
    Resolution: Fixed

Thanks for the updates, patch committed along with some other tests around mechanism selection.
Might be nice to remove the ASCII limitation, but I'd guess folks aren't too likely to hit
it so it should suffice for now.

> 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
>            Assignee: Robbie Gemmell
>             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


Mime
View raw message