I've made most of the changes I wanted but haven't had time to test them yet. Use at own risk:
http://cgit.freedesktop.org/~smcv/telepathy-gabble/log/?h=untested-otr Still to do: * testing (in particular, send "<" and "<a message that resembles HTML>" in both directions between Empathy and Pidgin, and check that neither is misinterpreted) * review from someone who understands libotr * Empathy: make sure OTR notifications are presented in a way that peers cannot fake. Because Empathy doesn't support HTML messages yet, distinctive formatting would be enough. * string-only handling of fingerprints (emit strings to D-Bus, parse hex -> binary when asked to trust a fingerprint from D-Bus) Nice to have, but not blockers: * TPAW UI for the enable-otr boolean parameter (for now, early adopters can turn it on with mc-tool - but I think real UI *is* a blocker for switching the default to be enabled) * Chan.I.Securable.{Encrypted,Verified} integration * enable-opportunistic-otr boolean parameter, and UI for the same (it will end up looking very similar to enable-otr, but with different handling in im-channel*.c) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/296867 Title: empathy needs to support OTR encryption To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs