Bug 25954

Summary: An API is needed for certificate verification
Product: Telepathy Reporter: Eitan Isaacson <eitan.isaacson>
Component: tp-specAssignee: Telepathy bugs list <telepathy-bugs>
Status: RESOLVED FIXED QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: normal    
Priority: medium CC: mail
Version: git master   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Eitan Isaacson 2010-01-08 17:21:58 UTC
When exchanging certificates, either during a server handshake, or an E2E handshake, there needs to be an API that would expose the certificate verification procedure to end-clients so that they could render the process interactive and allow the user to perform a "leap of faith".
Comment 1 Eitan Isaacson 2010-01-08 17:26:15 UTC
A branch of wocky that is accommodating the implementation of this is here:
http://git.collabora.co.uk/?p=user/eitan/wocky.git;a=summary

A telepathy-gabble branch is soon to follow..
Comment 2 Eitan Isaacson 2010-02-15 14:15:48 UTC
Updated spec is here:
http://git.collabora.co.uk/?p=user/eitan/telepathy-spec.git;a=summary

Gabble implementation is here:
http://git.collabora.co.uk/?p=user/eitan/telepathy-gabble.git;a=summary

Wocky changes are here:
http://git.collabora.co.uk/?p=user/eitan/wocky.git;a=summary

This all works together, awaiting review and cosimoc's XTLS implementation.
Comment 3 Cosimo Cecchi 2010-06-09 09:21:22 UTC
I am working on another approach for this, outlined here:

http://lists.freedesktop.org/archives/telepathy/2010-June/004621.html

Updated spec branch is here

http://git.collabora.co.uk/?p=user/cosimoc/telepathy-spec.git;a=shortlog;h=refs/heads/xtls-proposal

I yet have to implement it in Gabble.
Comment 4 Niklas Hambüchen 2010-10-15 14:08:10 UTC
What's going on in this bug? Is this still work in progress?
Comment 5 Eitan Isaacson 2010-10-15 14:15:33 UTC
This has been resolved elsewhere, see org.freedesktop.Telepathy.Channel.Type.ServerTLSConnection

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.