1661967 - Bug 1660687 broke OpenPGP migration with Enigmail 2.2.1

Status: RESOLVED WORKSFORME

(MailNews Core :: Security: OpenPGP, defect)

Description

[Kai Engert [:KaiE:]]

The change from bug 1660687 caused the Enigmail migrator Add-on version 2.2.1 to no longer work.

When attempting to start a migration, it fails with
"Uncaught (in promise) TypeError: getBondOpenPGP() is null"
"lazy loading couldn't get chrome://openpgp/content/modules/../BondOpenPGP.jsm"

Comment 1

[Kai Engert [:KaiE:]]

We have the choice to either backout bug 1660687, or to ask Patrick Brunschwig to include a fix and publish an updated version of the Enigmail Add-on.
Thanks to orange-vertex for reporting the issue, and thanks for Mark Banner to help with when analyzing the issue.

Comment 2

[Kai Engert [:KaiE:]]

It will be announced in this bug which approach we'll use to fix the issue (either release a Thunderbird update, or an Enigmail migrator Add-on update).

Comment 3

[Patrick Brunschwig]

I have uploaded on ATN a new version on of the Enigmail migrator (v2.2.2) with the fix that Kai sent me.

As soon as someone approves it, Enigmail will be compatible with TB 78.2.1.

Comment 4

[Kai Engert [:KaiE:]]

Patrick, thanks a lot. The updated Enigmail migrator version 2.2.2 has been published on addons.thunderbird.net

To everyone who experienced, or wants to avoid this bug:
Ensure you have version 2.2.2 (or newer) of Enigmail installed.

If Enigmail doesn't automatically (again) prompt you to migrate, you can manually access it.

On Windows and Linux, click the top area of the window with the right mouse button and select to enable the menu bar.
(On macOS the top menubar is always visible.)

In the top menu, select the Tools menu, and select the command "Migrate Enigmail Settings" (which is provided by the Enigmail Add-on).

A tab opens, which contains a button "Start Migration Now". If you select it, your migration should work.