 |
 |
On Fri, Sep 24, 2010 at 01:56:04AM +0200, Luke Howard wrote: > If you can get the gss_name_t object then you can use naming > extensions, otherwise you presumably need to wrap them up in a similar > SASL API. There will likely never be another standard SASL mechanism that isn't also a GS2 mechanism. Therefore there's no need to invent Cyrus SASL APIs equivalent to the GSS naming extensions -- just assume GS2, and ask for the gss_name_t of the peer. Nico --