[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [telepathy] [Bug 344144] Let the user choose, whether he wants logging of encrypted messages or not
From:       <ci3nte () gmail ! com>
Date:       2015-09-17 0:29:05
Message-ID: bug-344144-17878-s9kExHOCxh () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=344144

--- Comment #9 from ci3nte@gmail.com ---
I found this in the spec of the OTR-Proxy (ChannelProxy_Interface_OTR.xml from
ktp-common-internals):
<signal name="MessageReceived" tp:name-for-bindings="Message_Received">
      <tp:docstring xmlns="http://www.w3.org/1999/xhtml">
        <p>
          The same as:
          <tp:dbus-ref
namespace="ofdT.Channel.Interface">Messages</tp:dbus-ref>
          Plus:
          <p>The OTR interface adds some additional keys to message headers.
            Messages sent during an encrypted OTR session have an additional
            'otr-remote-fingerprint' header, whose string value is the
            human-readable hex form of an OTR fingerprint:</p>

          <code>
            {
            'message-type': Channel_Text_Message_Type_Normal,
            'message-sender': 42,               # Contact_Handle of
mercutio@example.com
            'otr-remote-fingerprint': '12345678 12345678 12345678 12345678
12345678',
            },
            {
            'content-type': 'text/plain',
            'content': 'O, then, I see Queen Mab hath been with you.',
            }
          </code>

          <p>Logging infrastructure MAY use these headers to associate
            conversations with OTR users in a secure way, or to avoid
            logging OTR conversations at all.</p>
...

Maybe this is useful. If I get it right, there is some telepathy service, which
is doing the normal jabber things, and a client service, which is doing the
user interaction and between of that is the otr proxy as an extra dbus-service
(although not specified from telepathy). How the logger interacts there? Is the
logger already behind the proxy?

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]