2007/3/27, Martijn Klingens <[EMAIL PROTECTED]>:

On Tuesday 27 March 2007 14:36, F. Scheffold wrote:
> That is not possible because the encryption key is only valid during the
> chat session.

Hmm. That complicates matters. :(

> One possibility would be to inform the user when he enables an otr chat
> session that history logs the messages. If he don't want that he could
> disable the history plugin. What do you think?

Perhaps it's possible to have a "bypassing" mechanism that history won't
log
OTR messages but still logs everything else? In that case it is a
checkbox 'Allow logging of messages' in the properties for OTR.


Hm,
I this would not be possible without changing the history soruce code.


Maybe even better is to extend Kopete::Message with a flag that marks a
message as 'sensitive' or 'encrypted' and then give History an option 'Log
encrypted messages as plain text' that can apply to both GPG and OTR?

--
Martijn
_______________________________________________
kopete-devel mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kopete-devel




A point to the problem to inform the user:
Before our 0.1 release I figure out how our plugin can get a list of the
loaded plugins and warn the user if history is enable.
The problem is that the headers I need to code this this, are marked as
NOINST in the automake options in kopete (I don't know at the moment which
it had been). So this could be quite a problem as long or plugin is
external.

Regard Frank
_______________________________________________
kopete-devel mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kopete-devel

Reply via email to