1638194 - Large OpenPGP public keyring not importing

Status: RESOLVED DUPLICATE of bug 1637508

(MailNews Core :: Security: OpenPGP, defect)

Description

[Jon]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:76.0) Gecko/20100101 Firefox/76.0

Steps to reproduce:

I am attempting to import my existing keyring into TB Beta's Key Manager.

I tried exports from Seahorse / "Passwords and Keys" (both .pgp and .asc/ascii-armored) as well as from an export from Enigmail (2.1.6 (20200328-0946) on TB 68.7.0 (64-bit)).

I tried smaller subset of exports (from seahorse) of ~100 keys which also didn't work (even after letting it idle for ~15 minutes).

I tried very small sets of 3 keys, which only worked when all keys were non-expired.

This is per request a new bug, spawned from comment #4 here https://bugzilla.mozilla.org/show_bug.cgi?id=1633249#c4

Platform: TB Beta 77.0b2 (64-bit) On Ubuntu 18.04

Actual results:

For the large (entire 50+MB keyring) and 100 key exports, nothing user-visible happened at all. No errors, status dialogs, and no keys imported.

For small sets of valid, non-expired keys, they worked - but importing 3 keys at a time against ~1000 keys is... not something I'd wish on anyone.

When importing a mix of expired and non-expired keys, I would get a confirmation dialog for only the first valid key, but none would be imported.

Looking in the debugging console, the errors of note:

"Cannot load required GPGME library"

As well as

CryptoAPI.sync() failed result: Error: "RNP.importToFFI failed"
importKeyBlock chrome://openpgp/content/modules/RNP.jsm:1216
importKeyFromFile chrome://openpgp/content/modules/cryptoAPI/RNPCryptoAPI.jsm:111
importKeyFromFile chrome://openpgp/content/modules/keyRing.jsm:350
EnigmailCommon_importKeysFromFile chrome://openpgp/content/ui/commonWorkflows.js:107
oncommand chrome://openpgp/content/ui/enigmailKeyManager.xhtml:1

CryptoAPI.sync() leaving interface.js:55:13
TypeError: res.importedKeys is undefinedkeyRing.jsm:360:9
importKeyFromFile chrome://openpgp/content/modules/keyRing.jsm:360
EnigmailCommon_importKeysFromFile chrome://openpgp/content/ui/commonWorkflows.js:107
oncommand chrome://openpgp/content/ui/enigmailKeyManager.xhtml:1

Expected results:

I would expect all keys, even expired keys, to be imported and visible in my keyring. I would expect some process/status dialog to show what's going, and possibly a report at the end on any keys which were unable to be imported (and therefore skipped over without stopping the process?)

VERY HAPPY to test further; but note that I am unable to share my public key keyring due to sensitive contacts and the social graph therein.

Potentially related feature trackers + bugs:
https://bugzilla.mozilla.org/show_bug.cgi?id=1588077
https://bugzilla.mozilla.org/show_bug.cgi?id=1595229
https://bugzilla.mozilla.org/show_bug.cgi?id=1637508

Comment 1

[Kai Engert [:KaiE:]]

Let's handle that in bug 1637508

Comment 2

[Kai Engert [:KaiE:]]

So maybe we shouldn't have closed this one, because it complains about "large" keyrings, while that other bug is mostly about nonworking individual keys.

We still don't have the ability to import large keys, but we have a workaround.

This new support article:
https://support.mozilla.org/en-US/kb/openpgp-thunderbird-howto-and-faq
has the following information:

"... you could try to use the Enigmail version 2.2.x migration Add-on for importing public keys into Thunderbird, even if you haven't used Enigmail before.

To do so, use Thunderbird 78 and search for the Enigmail Add-on. You'll be offered to install version 2.2.x. Once installed, you can manually access the command "Migrate Enigmail Settings" from Thunderbird's top menu bar, in the Tools submenu. Note that this may fail, depending on how you have set up GnuPG software on your computer, so it cannot be guaranteed that this approach works.

If you have correctly set up GnuPG software on your computer that the Enigmail migration Add-on can find, then it will import all public keys one by one from GnuPG into Thunderbird, without being affected by the mentioned sized limit. "