Problem Autocrypt sync with Enigmail

Hello!

After I enter Autocrypt sequence from Delta, Thunderbird replies “Error - the key could not be imported. The key is either not supported by your version of GnuPG, or it got corrupted.” I use standard Ubuntu without customizations.
Tried with both Android and Linux versions of Delta. (Linux synced with Android seamlessly.)

Tried to move keys manually (exported and imported files few times).
I get two private, and two public keys as result of Delta export. Private keys both 5.1KB, all keys indicate my email (when try to import), and the pairs have different ID’s. But “private-key-default.asc” doesn’t import via Enigmail Key Management! It just do nothing when I select the file, whilst other files triggers confirmation dialog.
private-key-1.asc
private-key-default.asc

Need your advice to solve the problem!

Ubuntu Thunderbird version is “60.6.1 (64-bit)”. Android Delta version is 0.304.0 .

Could you send the output of “gpg --list-packets” with your unimportable key?

could you maybe try to send Autocrypt setup message from Thunderbird and then type it into Delta?

Sorry, I’ve been AFK. And thank you for reply!

I tried Autocrypt setup in opposite direction while ago in testing environment, and it worked. But that way I will lose ability to read my older chats in Delta folder. And I did 4 confirmed user installs of Android app. ))

$ gpg --list-packets private-key-default.asc 
gpg: [don't know]: invalid packet (ctb=06)
gpg: [don't know]: invalid packet (ctb=32)
gpg: [don't know]: invalid packet (ctb=6d)
# off=0 ctb=c5 tag=5 hlen=3 plen=1368 new-ctb
:secret key packet:
	version 4, algo 1, created 1536278872, expires 0
	pkey[0]: [3072 bits]
	pkey[1]: [17 bits]
	skey[2]: [3070 bits]
	skey[3]: [1536 bits]
	skey[4]: [1536 bits]
	skey[5]: [1536 bits]
	checksum: dc59
	keyid: A7E9C4A23760B585
# off=1371 ctb=cd tag=13 hlen=2 plen=19 new-ctb
:user ID packet: "<skaunov@gmail.com>"
# off=1392 ctb=c2 tag=2 hlen=3 plen=444 new-ctb
:signature packet: algo 1, keyid A7E9C4A23760B585
	version 4, created 1536278908, md5len 0, sigclass 0x13
	digest algo 8, begin of digest cd 38
	hashed subpkt 2 len 4 (sig created 2018-09-07)
	hashed subpkt 9 len 4 (key does not expire)
	hashed subpkt 25 len 1 (primary user ID)
	hashed subpkt 27 len 1 (key flags: 03)
	hashed subpkt 11 len 5 (pref-sym-algos: 9 7 3 2 1)
	hashed subpkt 21 len 5 (pref-hash-algos: 8 9 10 11 2)
	hashed subpkt 22 len 1 (pref-zip-algos: 2)
	hashed subpkt 30 len 1 (features: 01)
	subpkt 16 len 8 (issuer key ID A7E9C4A23760B585)
	data: [3069 bits]
# off=1839 ctb=c7 tag=7 hlen=3 plen=1368 new-ctb
:secret sub key packet:
	version 4, algo 1, created 1536278908, expires 0
	pkey[0]: [3072 bits]
	pkey[1]: [17 bits]
	skey[2]: [3072 bits]
	skey[3]: [1536 bits]
	skey[4]: [1536 bits]
	skey[5]: [1536 bits]
	checksum: fa59
	keyid: E73298D09C7490D5
# off=3210 ctb=c2 tag=2 hlen=3 plen=421 new-ctb
:signature packet: algo 1, keyid A7E9C4A23760B585
	version 4, created 1536278911, md5len 0, sigclass 0x18
	digest algo 8, begin of digest 93 00
	hashed subpkt 2 len 4 (sig created 2018-09-07)
	hashed subpkt 9 len 4 (key does not expire)
	hashed subpkt 27 len 1 (key flags: 0C)
	subpkt 16 len 8 (issuer key ID A7E9C4A23760B585)
	data: [3071 bits]

Is there a chance that future versions of Delta will solve my problem? Could it be that Delta doesn’t export the private key properly?

note that if you import a key from Thunderbird into Android (Autocrypt Setup) then your old Delta key will still remain available so you can use it for decryption. Pretty soon, we are going to use https://github.com/rpgp/rpgp as our crypto engine in all Delta Chat releases – let’s see if the problem persists then.