[Bug 30460] Generate client side API for Chan.T.ServerTLSConnection and TLSCertificate

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Nov 26 15:04:36 CET 2010


Simon McVittie <simon.mcvittie at collabora.co.uk> changed:

           What    |Removed                     |Added
         AssignedTo|telepathy-bugs at lists.freede |simon.mcvittie at collabora.co
                   |sktop.org                   |.uk

--- Comment #2 from Simon McVittie <simon.mcvittie at collabora.co.uk> 2010-11-26 06:04:36 PST ---
One problem with this: adding TpTLSCertificate requires us to have an idea of
its life-cycle.

When a TLSCertificate is accepted or rejected, does it disappear from the bus
(i.e. it should be invalidated), or does it remain present?

(Currently, the answer in Gabble is: it stays.)

When a TLSCertificate appears, will it always be associated with a Channel?

(Currently, the answer in Gabble is: yes for ServerTLSAuthentication; no idea
for end-to-end encryption.)

When a TLSCertificate's Channel (if any) closes, should it be invalidated?

(Currently, the answer in Gabble is: yes.)

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