Bug 716523 - use an explicit sasl mechanism list
Summary: use an explicit sasl mechanism list
Keywords:
Status: CLOSED DUPLICATE of bug 846465
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: Development
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: mick
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-24 18:43 UTC by mick
Modified: 2012-12-07 18:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-07 18:23:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Apache JIRA QPID-3337 0 None None None Never

Description mick 2011-06-24 18:43:48 UTC
Currently, we default to using the system-default sasl mechanisms list.  That list will include GSSAPI if the package is installed on the user's system.  But merely installing the GSSAPI package does not prepare qpidd to use GSSAPI.  The user must perform specific config steps to make it work.  And, since GSSAPI will be selected before other mechanisms, this means that many users will see qpidd fail as soon as they try  --auth=yes  .

It also seems dangerous to allow PLAIN, since users who install qpidd will then have an insecure system by default.

By accepting the system-default list we are allowing too many user-surprises.

The solution is to explicitly control the mech list, probably only allowing a single mechanism such as DIGEST-MD5, and give the user sufficient instruction on how to set up other mechanisms when they are desired.

Comment 1 mick 2011-07-06 20:14:55 UTC
JIRA 3337

Comment 2 Justin Ross 2012-12-07 18:23:34 UTC

*** This bug has been marked as a duplicate of bug 846465 ***


Note You need to log in before you can comment on or make changes to this bug.