OTR not supported in Thunderbird with IRC chat
Categories
(Thunderbird :: Instant Messaging, defect)
Tracking
(Not tracked)
People
(Reporter: joysn71, Unassigned)
Details
Steps to reproduce:
I connected to some IRC channel at irc.oftc.net and want to use OTR with some users.
In the config editor, chat.otr.enable is set to true.
Command is shown in the chat window: ?OTRv2?
Actual results:
xxx@irc.oftc.net has requested an Off-the-Record (OTR) encrypted conversation. However, you do not have a plugin to support that.
Expected results:
OTR should have been used.
I use Thunderbird on Debian testing (Trixie), and libotr is installed:
libotr5/testing 4.1.1-5 amd64 [installed,automatic]
Comment 2•1 year ago
|
||
Check the console. Likely Thunderbird isn't finding the OTR library for some reason. (Distro issue?) Try with a build from https://thunderbird.net
I cleared the console before I switched from insecure to encrypted conversation, and the console remained empty. All log levels.
if I check the loaded libs of a running TB instance, they are loaded from /usr/lib/x86_64-linux-gnu:
WebExtens 27690 joysn mem REG 8,1 14472 3566455 /usr/lib/x86_64-linux-gnu/libplds4.so
WebExtens 27690 joysn mem REG 8,1 18272 3671377 /usr/lib/thunderbird/libmozwayland.so
WebExtens 27690 joysn mem REG 8,1 183040 3671375 /usr/lib/thunderbird/libmozsandbox.so
WebExtens 27690 joysn mem REG 8,1 1926256 3543707 /usr/lib/x86_64-linux-gnu/libc.so.6
WebExtens 27690 joysn mem REG 8,1 182776 3565411 /usr/lib/x86_64-linux-gnu/libgcc_s.so.1
WebExtens 27690 joysn mem REG 8,1 907784 3544631 /usr/lib/x86_64-linux-gnu/libm.so.6
WebExtens 27690 joysn mem REG 8,1 2493592 3542127 /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.33
And libotr is located in the same directory:
(base) joysn@laptop:~$ dpkg -L libotr5
/.
/usr
/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libotr.so.5.1.1
The stuff in OTRLib.sys.mjs seem to search for a libotr.so.5 if I understand correct, but I could not make the debugger halt on the lib lookup functions.
Comment 6•1 year ago
|
||
Try this in the error console and see what you get (Ctrl+Shift+J)
var { OTRLibLoader } = ChromeUtils.importESModule("resource:///modules/OTRLib.sys.mjs");
OTRLibLoader.init();
Comment 7•1 year ago
|
||
As far as I know we only support direct messages with OTR. From the initial report I'm not sure that's what's being attempted here?
Comment 8•1 year ago
|
||
Comment 9•1 year ago
|
||
(In reply to Martin Giger [:freaktechnik] from comment #7)
As far as I know we only support direct messages with OTR. From the initial report I'm not sure that's what's being attempted here?
OTR itself only supports direct (one-on-one) messages IIRC. Comment 0 does seem to imply that it is trying to negotiate it though. It could also be worth pulling the protocol log to see what's being sent over the wire (right click on the account and click copy debug log. This will likely have sensitive information in it).
Description
•