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

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Aug 31 15:44:36 CEST 2010


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

--- Comment #2 from Cosimo Cecchi <cosimoc at gnome.org> 2010-08-31 06:44:36 PDT ---
(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.

> It doesn't seem to be possible to "upgrade" an encrypted channel. For example,
> if we have a lockdown icon in Empathy's chat window or something, does that
> mean Empathy will have to request a new channel and replace it by the insecure
> one?

Right; I didn't originally take into account this use case, but as there's
really nothing in the interfaces requiring that a channel should only be
encrypted at creation time, this could probably be easily solved by adding a
method to the Encryptable interface:

- UpgradeToEncrypted (s: EncryptionInterface)

which at the same time sets EncryptionRequired to True, EncryptionInterface to
the provided interface, and fires up the authentication machine.

I will update my branch according to your comments.

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



More information about the telepathy-bugs mailing list