libunbound: couldn't open library / libunbound not correctly initialized #170

nataedu · 2019-09-12T18:32:48Z

I updated my Thunderbird to the last version and the DKIM verificator add-on stopped working. The status bar shows this brief error : Error in the DNS resolver.

If I open the error console setting the debeug levels I have the following errors :

DKIM_Verifier.libunbound	DEBUG	libunboundWorker: Posting exception back to main script: Error: libunbound not correctly initialized (ub_resolve missing)
libunbound.jsm:297
DKIM_Verifier.Verifier	ERROR	DKIM verifier internal error (DKIM_DNSERROR_UNKNOWN): libunboundWorker: Error: libunbound not correctly initialized (ub_resolve missing)(resource://dkim_verifier/helper.jsm:430:3) JS Stack trace: libunboundWorker.onmessage@libunbound.jsm:316:16
libunbound.jsm:316:16
DKIM_Verifier.Verifier	DEBUG	Exception on DKIM-Signature 1
dkimVerifier.jsm:1295

The text was updated successfully, but these errors were encountered:

lieser · 2019-09-12T19:04:21Z

Just tested it with TB 68.1.0, and could not reproduce it.

My guess is that loading the library failed. If the loading works, you should see the following in the logs:

9/12/2019, 20:50:49	DKIM_Verifier.libunbound	DEBUG	initialized
libunbound.jsm:197
9/12/2019, 20:50:49	DKIM_Verifier.libunbound	DEBUG	libunboundWorker: libunbound loaded
libunbound.jsm:297
9/12/2019, 20:50:51	DKIM_Verifier.libunbound	DEBUG	libunboundWorker: context created

Please make sure it still at the path specified by you.
If you used the one shipped by the DNSSEC Validator add-on it was probably removed from TB during the update. Check https://github.com/lieser/dkim_verifier/wiki/DNS#windows-use-the-libunbound-library-in-the-dnssec-validator on how to get the dll again.

nataedu · 2019-09-12T19:24:35Z

I double checked the path and restarted the computer (on Windows sometimes that does wonders), and the error changed :
DKIM_Verifier.libunbound FATAL Exception in libunboundWorker: DKIM verifier internal error (DKIM_DNSERROR_UNKNOWN): libunboundWorker: Error: couldn't open library C:\Program Files\Mozilla Thunderbird\extensions\libDNSSECcore-windows-x86.dll: error 193(resource://dkim_verifier/helper.jsm:430:3) JS Stack trace: libunboundWorker.onmessage@libunbound.jsm:316:16

The .dll is at the right location, so I don't understand what is wrong.
I use TB with the x64 version.

lieser · 2019-09-12T19:29:11Z

Are you sure you are using a dll for x64?

See also #122 (comment) for a link to a x64 dll.

lieser · 2019-09-21T17:03:28Z

@nataedu Could you fix the issue? If yes, please close this.

SilmorSenedlen · 2019-09-22T22:06:46Z

@lieser I think it's need to update wiki section about libunbound configuration.
Something like this:

Go to download page of Unbound DNS resolver: https://nlnetlabs.nl/projects/unbound/download/
Download "Binaries (no install)" zip package depending on your version of Thunderbird: 32-bit(x86) or 64-bit(x64)
Open downloaded archive and go to libunbound sub-directory unbound-1.9.3.zip\libunbound\
Extract following file:

For 32-bit(x86):

libcrypto-1_1.dll
libssl-1_1.dll
libunbound-8.dll

Or for 64-bit(x64):

libssl-1_1-x64.dll
libcrypto-1_1-x64.dll
libunbound-8.dll

To your Thunderbird profile extensions directory.

For example:

C:\Users\your_profile_name\AppData\Roaming\Thunderbird\Profiles\profile_name\extensions\

Open DKIM Verifier add-on options.
Go to General >> DNS
Select libunbound in Resolver dropdown list.
Set Path as extensions/libunbound-8.dll and Path relative to profile directory checkbox.

Tested on Thunderbird 68.1.0 (64-bit) with DKIM Verifier 3.0.1 and DLL's from Unbound 1.9.3 x64 package.

nataedu · 2019-09-23T15:52:28Z

So @lieser I couldn't fix the issue, and after following step by step the instructions given by @SilmorSenedlen I could not fix the issue. I still get an error :
23/09/2019, 17:40:36 DKIM_Verifier.libunbound FATAL Exception in libunboundWorker: DKIM verifier internal error (DKIM_DNSERROR_UNKNOWN): libunboundWorker: Error: couldn't open library C:\Users\<user>\AppData\Roaming\Thunderbird\Profiles\<profile>\extensions/libunbound-8.dll: error 126(resource://dkim_verifier/helper.jsm:430:3) JS Stack trace: libunboundWorker.onmessage@libunbound.jsm:316:16

I am also in Thunderbird 68.1.0 (64-bit) with DKIM verifier 3.0.1 and downloaded the DLL from Unbound 1.9.3 for the x64 architecture

SilmorSenedlen · 2019-09-23T16:29:15Z

@nataedu looking more closely to your DLL's path from the log:

C:\Users\<user>\AppData\Roaming\Thunderbird\Profiles\<profile>\extensions/libunbound-8.dll

on the part \extensions/

It's strange. In my case extensions/libunbound-8.dll and Path relative to profile directory checkbox work well.

Try to change / to \ in the Path

Upd. In my case work well either way.

nataedu · 2019-09-23T16:36:25Z

I know. I put the relative path as you had suggested, and tried both '\' and '/'. The file is there but I get the same error

SilmorSenedlen · 2019-09-23T16:44:25Z

@nataedu
Try to remove add-on and delete all preferences with prefix extensions.dkim_verifier from Options >> Advanced >> Config Editor(about:config) and restart TB.

nataedu · 2019-09-23T17:32:29Z

I tried and I still get the same error.

d4k0 · 2019-09-23T19:13:40Z

@nataedu
I have the exact same problem with Thunderbird 68.1.0 x64, DKIM verifier 3.0.1 and Unbound 1.9.3 x64. Somehow the extension can't load the DLL:

23.9.2019, 21:04:20 DKIM_Verifier.libunbound FATAL Exception in libunboundWorker: DKIM Verifier Interner Fehler (DKIM_DNSERROR_UNKNOWN): libunboundWorker: Error: couldn't open library C:\Users\<user>\AppData\Roaming\Thunderbird\Profiles\wnxacr0f.default\extensions\libunbound-8.dll: error 126(resource://dkim_verifier/helper.jsm:430:3) JS Stack trace: libunboundWorker.onmessage@libunbound.jsm:316:16 libunbound.jsm:322

The path that is shown in the log is correct. Before the 64-bit version of Thunderbird existed, it worked with the x86 version of libunbound if I remember correctly (I responded in a ticket back then).

I will probably test it again with a portable version of Thunderbird and a new profile this weekend.

lieser · 2019-09-23T23:03:05Z

I did some experimenting, and found that the loading of the dependent libraries has some weird behavior. If it was one loaded by TB, TB seems to always try to load it from the same path again. Restarting TB, or even Windows did not change anything for me.

For testing I now added the ability to explicitly load more libraries before libunbound.
Please try it with dkim_verifier@pl-beta.zip (This is for TB68)

You also need to specify the path to the dependencies, separated by ;, in the correct order.
E.g.:

extensions/libcrypto-1_1-x64.dll;extensions/libssl-1_1-x64.dll;extensions/libunbound-8.dll

If this does still not help, please enable tracing by setting extensions.dkim_verifier.logging.console to Trace, and post the DKIM_Verifier.libunbound messages.

Also try to load the libraries in the above order with ctypes.open(<full path>).

d4k0 · 2019-09-24T18:31:18Z

@lieser
Nice, it seems to work now! When the first request is made, Windows Firewall now also asks for permission.

nataedu · 2019-09-28T14:58:50Z

@lieser Works for me too! I have also the request from the Windows Firewall.
Thanks for the help!

Pascal666 · 2020-03-05T04:44:08Z

Go to download page of Unbound DNS resolver: https://nlnetlabs.nl/projects/unbound/download/

Download "Binaries (no install)" zip package depending on your version of Thunderbird: 32-bit(x86) or 64-bit(x64)

The DLLs appear to no longer be available on that page. Does anyone know the new location or have a copy they can post?

SilmorSenedlen · 2020-03-05T08:00:40Z

Does anyone know the new location

Sadly not. We should ask the developers of unbound.

have a copy they can post?

Below are archives with 3 previously mentioned files from the last published binary version(1.9.3).
libunbound_files_1.9.3_x86.zip
libunbound_files_1.9.3_x64.zip

lieser self-assigned this Sep 12, 2019

lieser added the bug label Sep 12, 2019

SilmorSenedlen mentioned this issue Sep 22, 2019

Provide 64-bit libunbound libraries for Windows #122

Closed

lieser mentioned this issue Sep 23, 2019

[bug] Exception in libunboundWorker - libunbound not correctly initialized (ub_resolve missing) #179

Closed

lieser changed the title ~~Bug on DKIM verification with libunbound in thunderbird 68.1.0~~ libunbound: couldn't open library / libunbound not correctly initialized Sep 23, 2019

lieser added this to the 3.0.2 milestone Sep 23, 2019

nataedu closed this as completed Sep 28, 2019

lieser modified the milestones: 3.0.2, 2.2.0 Jan 5, 2020

lieser mentioned this issue May 3, 2021

DKIM looses DNS if computer sleeps and change network when restarting #257

Closed

lieser mentioned this issue Sep 17, 2023

Using libunbound results in an internal error #385

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

libunbound: couldn't open library / libunbound not correctly initialized #170

libunbound: couldn't open library / libunbound not correctly initialized #170

nataedu commented Sep 12, 2019

lieser commented Sep 12, 2019

nataedu commented Sep 12, 2019

lieser commented Sep 12, 2019

lieser commented Sep 21, 2019

SilmorSenedlen commented Sep 22, 2019 •

edited

nataedu commented Sep 23, 2019

SilmorSenedlen commented Sep 23, 2019 •

edited

nataedu commented Sep 23, 2019 •

edited

SilmorSenedlen commented Sep 23, 2019 •

edited

nataedu commented Sep 23, 2019

d4k0 commented Sep 23, 2019

lieser commented Sep 23, 2019 •

edited

d4k0 commented Sep 24, 2019 •

edited

nataedu commented Sep 28, 2019

Pascal666 commented Mar 5, 2020

SilmorSenedlen commented Mar 5, 2020 •

edited

libunbound: couldn't open library / libunbound not correctly initialized #170

libunbound: couldn't open library / libunbound not correctly initialized #170

Comments

nataedu commented Sep 12, 2019

lieser commented Sep 12, 2019

nataedu commented Sep 12, 2019

lieser commented Sep 12, 2019

lieser commented Sep 21, 2019

SilmorSenedlen commented Sep 22, 2019 • edited

nataedu commented Sep 23, 2019

SilmorSenedlen commented Sep 23, 2019 • edited

nataedu commented Sep 23, 2019 • edited

SilmorSenedlen commented Sep 23, 2019 • edited

nataedu commented Sep 23, 2019

d4k0 commented Sep 23, 2019

lieser commented Sep 23, 2019 • edited

d4k0 commented Sep 24, 2019 • edited

nataedu commented Sep 28, 2019

Pascal666 commented Mar 5, 2020

SilmorSenedlen commented Mar 5, 2020 • edited

SilmorSenedlen commented Sep 22, 2019 •

edited

SilmorSenedlen commented Sep 23, 2019 •

edited

nataedu commented Sep 23, 2019 •

edited

SilmorSenedlen commented Sep 23, 2019 •

edited

lieser commented Sep 23, 2019 •

edited

d4k0 commented Sep 24, 2019 •

edited

SilmorSenedlen commented Mar 5, 2020 •

edited