Re: Bus authentication on Windows v2.0
LRN <[email protected]>
| Newsgroups | gmane.comp.freedesktop.dbus |
|---|---|
| Message-ID | <[email protected]> |
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 _______________________________________________ dbus mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dbus
signature.asc
(application/pgp-signature, 473 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXZTngAAoJEOs4Jb6SI2CwxkkH/0h7hK+EIHbZmnVZTqC8aFF+ mo5XPZDDtI3XuyYhnjSm2Mt6FX8zo3NDpvDnRju89sZfJ3EHVUTh49rBcgYP2nPN u2Wg2bV+1AwnGHrXSimCtWa2MzX56j4VYMEyQcS+jFfIyoI6A3RmKOazBy8NpE2W K/O2T3w5FVNv3h2qEtTq7l1V1vwNvHEhH1a/wR8OkHdhcVSgr/AnQtmcD4tKDZF6 7T3GXfWzeXXKynJvvAmGqYrsmJRH67Od2XIMkluHNLES7Rg41iQCLZ04+G8cdkDJ tJeTjmBZ5CSdBlqIEThoT0iknLwl40XwkroXdnXWye0g9Z1iw/wAymGIas85Rvc= =rwlV -----END PGP SIGNATURE-----