[PATCH] Add support for SASL EXTERNAL to libads
abartlet at samba.org
Mon Jun 9 02:55:58 GMT 2003
On Mon, 2003-06-09 at 12:51, Luke Howard wrote:
> >Given you just added support in the SASL code for 'external', why do we
> >need to explicitly enforce it here? Won't it be negotiated already? Or
> >am I missing something?
> I added the flag to allow the caller to force the use of EXTERNAL over
> GSS-SPNEGO or GSSAPI.
> Note that this patch may not actually be that useful; I'm submitting it
> in order to comply with our obligations under the GPL.
Well, I think it is a useful patch, as we move to using libads for our
passdb code. SASL allows the client to chose which mechanism to use
first, doesn't it? This should allow us to express a preference order
in the SASL table, and therefore allow this... (possibly enabled by
this flag - indeed we could do PLAIN SASL the same way...)
Andrew Bartlett abartlet at pcug.org.au
Manager, Authentication Subsystems, Samba Team abartlet at samba.org
Student Network Administrator, Hawker College abartlet at hawkerc.net
http://samba.org http://build.samba.org http://hawkerc.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.samba.org/archive/samba-technical/attachments/20030609/93f6d4e3/attachment.bin
More information about the samba-technical