[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

--- Comment #38 from Simon McVittie <simon.mcvittie at collabora.co.uk> 2010-11-23 04:15:00 PST ---
> +        <tp:dbus-ref namespace="ofdT">Channel</tp:dbus-ref>s. The two
> +        properties are immutable and can be used to make decisions on
> +        how cautious to be about transferring sensitive data.</p>

In cosimoc's e2e encryption branch, these properties are mutable but can only
get more secure. I think that's correct in general. When securing a Text
channel, say, I think we probably do want them mutable - it starts off
unsecured, you upgrade it to e2e security, and the channel remains the same,
but the message path behind the scenes changes to a secure one.

My suggested compromise was to have them tp:immutable="sometimes", and specify
that for the special case of ServerAuthentication channels, they are indeed
immutable.

When we support e2e encryption, we can also add the securing state (not tried
-> trying -> succeeded or failed, where Encrypted and Verified stop changing
after the state has reached succeeded).

> </tt>". where

(in DefaultUsername) Nitpicking: dot -> comma

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