#1019 closed enhancement (fixed)
please allow "otr disconnect *" or do it on quit
| Reported by: | Jan Braun | Owned by: | wilmer |
|---|---|---|---|
| Priority: | wishlist | Milestone: | |
| Component: | OTR | Version: | 3.0.5 |
| Keywords: | patch | Cc: | janbraun@… |
| IRC client+version: | Client-independent | Operating System: | Linux |
| OS version/distro: |
Description
Since the OTR library doesn't gracefully handle a client going away and forgetting about an active OTR session[1], I'm using the workaround of "/alias quit /msg &bitlbee otr disconnect nick1 ; /msg &bitlbee otr disconnect nick2 ; /msg &bitlbee otr disconnect nick3 ; /wait 500 ; /quit" in my irc client. It would be nice to be able to tell bitlbee-otr to disconnect all active conversations.
Alternatively, it may be better to implement doing that automatically if the irc client disconnects. However, other otr-enabled clients don't seem to close their conversations on quit either, probably because it's introducing new network traffic.
[1] The other side will stay in "a connection exists" state and complain about new incoming messages being plaintext. In particular, it will not recognize the whitespace marker on them and not restart encryption.
Attachments (1)
Change History (7)
Changed at 2013-01-14T19:43:21Z by
| Attachment: | bitlbee.disconnectall.patch added |
|---|
comment:1 Changed at 2013-01-14T19:50:17Z by
Just wrote a patch for it. Written and tested against 3.0.5, but applies and compiles cleanly against 3.2 .
comment:3 Changed at 2014-02-07T15:05:07Z by
| Status: | new → accepted |
|---|
Indeed, not disconnecting OTR sessions on quit was an oversight and should be done for the reason you state. I've checked pidgin-otr and it does it this way. Also thanks for the patch, I'll add that too.
comment:4 Changed at 2014-02-07T16:04:11Z by
| Owner: | changed from pesco to wilmer |
|---|---|
| Status: | accepted → assigned |
Done, with a few adjustments to the code. Pull from the usual place:
patch v1