I can't attach a public key received by email

[michaelbr]

This is my environment:
Ubuntu 16.04
Enigmail 2.0.9
TB 60.2.1
I received an email with a public key, on top of the email says: Enigmail A key was found in the message body. Click 'Import Key' to import the key.
I went to the Enigmail menu in TB, but there's no such Import Key command, so I tried to copy the public key to clipboard and import it from there, after importing (did not receive any error message), the new key did not show up, what am I missing? Is my procedure correct? I did install Enigmail using sudo apt-get install enigmail

[Patrick Brunschwig]

See attached screenshot. The "Import Key" button is in the Enigmail bar.

[michaelbr]

Hi Patrick, thanks for your reply, sorry to take so long, I had activated my dark theme, that's why I can't see the button, after disabling the dark theme, I saw the button, but when I click on it, nothing happened, the details one, when clicked, a drop down is shown, but from the Show Key Properties down, all are grayed out.

[Patrick Brunschwig]

The "Details" button will only have active entries after the key was imported. The button to use is really "Import Key". After you clicked it, there should be a dialog asking you if you want to import the key.

[michaelbr]

Sorry Patrick, but there's no dialog asking for import. Is there anything I can do to troubleshoot this problem? I even disabled uBlock and CookieAutoDelete.

[Patrick Brunschwig]

I suspect that there's some error in this case. Can you attach a debugging log file?

[michaelbr]

Thanks for the tip, here's the log file

[Kevin Moraga]

Hi,
I can confirm the same issue on:
TB: 60.4.0
Enigmail: 2.0.9
Ubuntu: 18.04

[Kevin Moraga]

Also tested in Enigmail: 2.0.8 with the same error. Import button doesn't work.

[Kevin Moraga]

2019-02-14 13:50:15.415 [DEBUG] enigmailMsgHdrViewOverlay.js: this.updateHdrIcons: exitCode=-1, statusFlags=29360128, keyId=, userId=, A key was found in the message body. Click 'Import Key' to import the key
2019-02-14 13:50:15.415 [DEBUG] enigmailMessengerOverlay.js: createArtificialAutocryptHeader
2019-02-14 13:50:15.415 [DEBUG] keyRing.jsm: getKeyById:
2019-02-14 13:50:15.416 [DEBUG] autocrypt.jsm: processAutocryptHeader(): from=Luis Castillo lucastillomorera@gmail.com
2019-02-14 13:50:15.416 [DEBUG] autocrypt.jsm: openAutocryptDb()
2019-02-14 13:50:15.416 [DEBUG] autocrypt.jsm: _openAutocryptDb_inner()
2019-02-14 13:50:15.417 [DEBUG] enigmailMsgHdrViewOverlay.js: this.updateMsgDb
2019-02-14 13:50:15.417 [DEBUG] autocrypt.jsm: got 0 rows
2019-02-14 13:50:15.417 [DEBUG] autocrypt.jsm: appendUser(XXXXXX@gmail.com)
2019-02-14 13:50:15.417 [DEBUG] key.jsm: getKeyListFromKeyBlock
2019-02-14 13:50:15.417 [DEBUG] autocrypt.jsm: OK - closing connection
2019-02-14 13:50:15.418 [DEBUG] autocrypt.jsm: checkDatabaseStructure
2019-02-14 13:50:15.418 [DEBUG] autocrypt.jsm: checkDatabaseStructure
2019-02-14 13:50:15.419 [DEBUG] autocrypt.jsm: checkDatabaseStructure - success
2019-02-14 13:50:15.419 [DEBUG] autocrypt.jsm: findUserRecord
2019-02-14 13:50:15.419 [DEBUG] autocrypt.jsm: checkDatabaseStructure - success
2019-02-14 13:50:15.419 [DEBUG] autocrypt.jsm: findUserRecord
2019-02-14 13:50:15.419 [DEBUG] autocrypt.jsm: got 0 rows
2019-02-14 13:50:15.419 [DEBUG] autocrypt.jsm: appendUser(XXXXXX@gmail.com)
2019-02-14 13:50:15.419 [DEBUG] key.jsm: getKeyListFromKeyBlock
2019-02-14 13:50:15.420 [DEBUG] autocrypt.jsm: OK - closing connection
2019-02-14 13:50:15.420 [DEBUG] autocrypt.jsm: got 0 rows
2019-02-14 13:50:15.420 [DEBUG] autocrypt.jsm: appendUser(XXXXX@gmail.com)
2019-02-14 13:50:15.421 [DEBUG] key.jsm: getKeyListFromKeyBlock
2019-02-14 13:50:15.421 [DEBUG] autocrypt.jsm: OK - closing connection
2019-02-14 13:50:18.645 [DEBUG] enigmailMessengerOverlay.js: updateOptionsDisplay:
2019-02-14 13:50:18.646 [DEBUG] funcs.jsm: collapseAdvanced:
2019-02-14 13:50:20.821 [DEBUG] enigmailMessengerOverlay.js: updateOptionsDisplay:
2019-02-14 13:50:20.821 [DEBUG] funcs.jsm: collapseAdvanced:
2019-02-14 13:50:22.336 [DEBUG] enigmailHelp.js: enigLoadPage
2019-02-14 13:50:22.336 [DEBUG] windows.jsm: getFrame: name=contentFrame

[Kevin Moraga]

I found the following things:
1) Attached public key (.asc), works fine
2) If the key is attached as text within the email and using multipart (html & text), enigmail reads only the html section. And if there are some problems with the encoding and html tags, it fails, and ignore the plain/txt part, which is more easy to parse.

Attached are some files with the clasification:

[Patrick Brunschwig]

Yes, it's expected that keys in HTML mail bodies may not be correctly imported. Enigmail does not have access to the plaintext message part.

The correct way to attach a key is to attach it, and not to embed it in the text body. Enigmail offers the functions Attach my public key and Attach public keys (both available from the Enigmail menu in the message composition window) for this purpose. Such attached keys are easily discoverable for Enigmail (any most other email clients) and can be automatically imported.