[Bug 29904] Support end-to-end encryption and authentication

[bugzilla-daemon at freedesktop.org]

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

--- Comment #4 from Simon McVittie <simon.mcvittie at collabora.co.uk> 2010-09-01 04:22:30 PDT ---
(In reply to comment #2)
> (In reply to comment #1)
> > Ch.Type.ClientAuthentication: it would be good to document what is TargetHandle
> > and TargetHandleType will look like. 0 and 0 ?
> 
> Yeah, that's the idea; the ClientAuthentication channel is anonymous and the
> requesting channel would be added to its TargetChannels.

I think it would make sense to have TargetHandleType=CONTACT and TargetHandle
set, if it is guaranteed that the THT and TH of every target channel will match
those values. In practice, I suspect that will always be true, since we are
after all authenticating with a specified client?

Client already means something different in Telepathy, so I wonder whether we
should be calling these something different, perhaps chosen from:

* EndToEndAuthentication
* EndAuthentication
* PeerAuthentication

I quite like PeerAuthentication as a name for this, actually.

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