OTR conversations get refreshed when doing a CTCP ping to someone using weechat-OTR and with whom you have a session

[koolfy]

The title is pretty self-explanatory.

I think the other side doesn't understand the query and asks for a conversation refresh (because it never answers)

This is probably just about making sure once and for all ctcp queries don't interfere with ongoing OTR sessions.

[tribut]

Can't reproduce. With latest master (v1.4.0-12-g01adb83) i just get

Unencrypted message received:  ping

which I think is correct unless we decide to handle \x01ping\x01 in a special way.

[mmb]

@koolfy Is this still something you think we should handle?

[Mikaela]

Reproduced with testing #111

2015-02-11 09:24:49+0200 < nils_2> Unencrypted message received: PING 1423639489 287454
2015-02-11 09:24:56+0200 :! otr !: Private conversation has been refreshed.

WeeChat 1.2-dev and latest otr.py from /script.

[mmb]

I can't reproduce the "unencrypted message received" unless the ping is the first message of the conversation and require_encryption is turned on. If there is an established OTR session ctcp goes through the encrypted channel and appears to work.

Do you know if the CTCP messages causing the problem are using NOTICE or anything other than PRIVMSG?