Error: rnp_key_protect failed
Categories
(MailNews Core :: Security: OpenPGP, defect, P1)
Tracking
(Not tracked)
People
(Reporter: ak.bugzilla, Unassigned)
References
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.89 Safari/537.36 Edg/84.0.522.40
Steps to reproduce:
Import a personal key via Add Key button on the account settings page. Select the key to import and check the acceptance box. Click continue. If the key is protected with a password, I get prompted with a password dialog.
Actual results:
Next dialog shows "Importing your OpenPGP Keys..." and a loading symbol. It never finishes this action. Only way to cancel this is to close the tab. Error console shows: CryptoAPI.sync() failed result: Error: rnp_key_protect failed
Expected results:
Should properly import the key. Test with the same key was successful in TB daily 80.0a1.
|
||
Comment 1•5 years ago
|
||
Can you please tell us more about the key and file you're importing?
Which software was used to create it?
Does it have any special structure? (Subkeys, algorithms)
Are you importing ascii armor or a binary file?
|
|
||
Updated•5 years ago
|
The key was originally created with Enigmail and is already expired. I used the key manager on TB 78.0.1 to backup it in the standard ASCII Armored File format from one PC and transfer it to another.
It is a primary key with one subkey, algorithm RSA 2048.
I tried the following procedure:
I created a new key with the key wizard of TB 78.0.1, made a backup and deleted the key. I always kept the default settings. Then I tried to re-import the key. I can import the key in TB daily 80.0a1 and Beta 79b2, but not in 78.0.1 (import through key wizard, import through OpenPGP key manager works).
I originally updated TB 68 to TB 78. In TB 78 the OpenPGP functionality is disabled by default. I used the Enigmail migration tool which enabled OpenPGP. Is it possible that this tool somehow missed to enable a necessary setting? I couldn't find any differences in the config editor between 78.0.1 and 80.0a1 when searching for OpenPGP values.
Can you reproduce this with your set-up that you created in Bug 1656401 ?
|
|
||
Updated•5 years ago
|
|
|
||
Comment 5•5 years ago
|
||
Can you please try again with the newer version 78.1.1 ?
Still the same behaviour, also with the new import wizard in the key manager.
|
|
||
Comment 7•5 years ago
|
||
Ok, issue understood, explained in bug 1656287 comment 15.
Description
•