Bus authentication on Windows v2.0

[LRN]

On 07.06.2016 15:02, Simon McVittie wrote:
> On 06/06/16 20:31, LRN wrote:
>> DBUS_WINDOWS_SSPI_* would work as well (there's no length limit on
>> mechanism name, is there? also, should it always be all all-caps?)
> 
> I don't know. The SASL RFC (RFC 4422 I think) would tell you. All-caps
> does seem to be conventional - EXTERNAL, DIGEST and ANONYMOUS are among
> the standard mechanisms.
> 
> If you are inventing a D-Bus-specific SASL mechanism (and not, for
> instance, writing a standards-track RFC for SSPI SASL mechanisms in
> general) then it would make sense for it to be somewhat consistent with
> the only other D-Bus-specific SASL mechanism, which is DBUS_COOKIE_SHA1.
> 

Bugzilled[1] it.

[1] https://bugs.freedesktop.org/show_bug.cgi?id=96577

-- 
O< ascii ribbon - stop html email! - www.asciiribbon.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <https://lists.freedesktop.org/archives/dbus/attachments/20160618/1cbecba7/attachment.sig>