Summary: | Support interactive TLS certificate verification on connection | ||
---|---|---|---|
Product: | Wocky | Reporter: | Cosimo Cecchi <cosimoc> |
Component: | General | Assignee: | Telepathy bugs list <telepathy-bugs> |
Status: | RESOLVED FIXED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Cosimo Cecchi
2010-07-12 04:03:32 UTC
Needs some cleanups (introduces tabs).. I'm also not sure about the API it introduces.. It might be overkill but it would be nicer to have an object with some standard async functions that get called as a request to verify the ssl thing.. Where the default implementation of the object is what's currently done in wocky.. Vaguely similar to how we do interactive authentication via the AuthRegistry. How does that sound ? I updated my wocky code to this proposal, and I also took the opportunity to do some refactor of the connector code, splitting the TLS connection bits into its own object (that works a bit like WockySaslAuth). My new code is in the 'tls-connection2' branch of my wocky repo, here [1]. Review welcome :) [1] http://git.collabora.co.uk/?p=user/cosimoc/wocky.git;a=shortlog;h=refs/heads/tls-connection2 This has been now merged to master, closing as FIXED. |
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.