A2Module is not defined

[k-wax]

I'm running a nextcloud instance on yunohost that stores my kdbx. I set Tusk to look for it via WebDav, all good here. After unlocking the db i get an error: "A2Module is not defined" and the db stays locked. Is this an apache2 configuration issue?

[ghost]

I've been getting the exact same issue for a while now in Firefox. I thought it was just something unique to my PC because I hadn't refreshed Firefox in a while. Except I just did that and the error still persists:

I don't get this error in Opera, Chrome or Vivaldi.

[subdavis]

Great, so it's a Firefox related issue.

Thanks for the bug report. I'll check it out.

[k-wax]

Oops, yes. Firefox 63.0 on KDE Neon stable.

[tasoili]

Same problem on 64b4

[benclark06]

Same problem on firefox 63.0.1 on windows

[spvkgn]

Same issue on FF63 Linux with Gdrive

[jasperweiss]

I was suspecting A2Module was a reference to Argon2.
Indeed, opening a database with AES-KDF as its key transformation function opens just fine. It's databases that are configured with Argon2 that causes the problem on firefox.

[subdavis]

I'm really struggling with this one. Tusk 2018.9.27 works on FF 61, breaks on 63. Couldn't find anything helpful in the 62 or 63 changelog to see if wasm loading was altered.

According to the debug logs, argon2.wasm fails to load at all.

I need to go study what @antelle did in keeweb/keeweb@32dcb31 -- I haven't really touched the argon2 bits since I added them last July, and I followed his lead. It looks like things changed last November and I never noticed the changes.

This may also solve #268, #212

Edit: I don't know why I'm having an issue with loading these scripts, but Antelle appears to side-step that by pre-compiling the webassembly in with require.js.

[alensiljak]

As reported in #276, I'm also experiencing the same issue with the current Firefox Developer.

[subdavis]

Thanks @mistery. I've done a bit more research since the last comment, and I believe this can be solved with the wasm-loader webpack plugin.

Sorry this has taken a while to get to. I know it's a critical issue. As mentioned above, Firefox changed something between 61 and 63 that breaks WASM compilation, but they didn't mention it in the changelog.

[alensiljak]

No worries. I'll check again in the near future. If you need me to test some pre-release version, I'd be happy to, as well.

[subdavis]

This has been fixed and updated in the firefox store: version 2018.11.28

Please, PLEASE let me know if this does not solve your issue.

[alensiljak]

Thanks a lot! I can confirm that it works now (for me, at least). Now I can try out the features of the addon. So far it looks and behaves great.

[epasch]

This is now working for me as well. Thanks!