[Bug 14003] Chan.T.ServerAuthentication, Chan.I. SASLAuthentication — authenticate with server interactively

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=14003

Jonny Lamb <jonny.lamb at collabora.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                URL|http://git.collabora.co.uk/ |http://git.collabora.co.uk/
                   |?p=user/smcv/telepathy-spec |?p=user/jonny/telepathy-spe
                   |-smcv.git;a=shortlog;h=refs |c.git;a=shortlog;h=refs/hea
                   |/heads/sasl                 |ds/sasl

--- Comment #37 from Jonny Lamb <jonny.lamb at collabora.co.uk> 2010-11-23 04:00:06 PST ---
(In reply to comment #31)
> Perhaps this?
> 
> Chan.I.Securable

I've done this.

(In reply to comment #34)
> Status needs an attribute so it pluralizes to Statuses rather than Statuss.

Done.

> we could even drop SASLContext in its entirety?

Done.

> It makes no sense to call AbortSASL from the Succeeded state: that should raise
> NotAvailable. Whether it makes sense in Client_Accepted is debatable; eeejay's
> implementation fails there, too.

Done.

(In reply to comment #36)
> AuthorizationIdentity isn't really sufficient; we also need DefaultUsername,
> for use with SASL mechanisms that deal with a "simple username" as defined in
> RFC 4422 §2. RFC 3920 §6.3 suggests that we should also be providing the UI
> with a service name, which is "xmpp" for XMPP.

Done!

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.