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.
NOTE – I am also allowing ANONYMOUS, because some python tools do not yet know how to send credentials, and this will allow them to continue working.
|Field||Original Value||New Value|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|
|Status||Resolved [ 5 ]||Closed [ 6 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|1h 1m||1||michael j. goulish||06/Jul/11 21:14|
|753d 22h 40m||1||Justin Ross||29/Jul/13 19:54|