Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Decryption using smartcard fails: openpgp: Decrypted; key=, plainText= decryption.sys.mjs:316:14

  • 2 Antworten
  • 0 haben dieses Problem
  • Letzte Antwort von Matt

more options

Possibly related to my general opengpg+smartcard configuration see Separate ticket because the call stacks are quite different.

openpgp: Cannot decrypt message. decryption.sys.mjs:528:16 openpgp: Decrypted; key=, plainText= decryption.sys.mjs:316:14 openpgp: Extra decryption details: {"encryptedTo":{"myRecipKey":{},"allRecipKeys":[{"keyId":"B8DE03DA7CEA42B2","primaryKeyId":"A9CB8CB214D427B2"},{"keyId":"B8DE03DA7CEA42B2","primaryKeyId":"A9CB8CB214D427B2"}]},"packetDump":":armored input\n

off 0: packet header 0xc1c14c (tag 1, len 524)\n

Public-key encrypted session key packet\n

   version: 3\n
   key id: 0xb8de03da7cea42b2\n
   public key algorithm: 1 (RSA (Encrypt or Sign))\n
   encrypted material:\n
       rsa m: 4095 bits\n
off 527: packet header 0xc1c14c (tag 1, len 524)\n

Public-key encrypted session key packet\n

   version: 3\n
   key id: 0xb8de03da7cea42b2\n
   public key algorithm: 1 (RSA (Encrypt or Sign))\n
   encrypted material:\n
       rsa m: 4090 bits\n
off 1054: packet header 0xd2c156 (tag 18, len 534)\n

Symmetrically-encrypted integrity protected data packet\n \n "} decryption.sys.mjs:331:16

Possibly related to my general opengpg+smartcard configuration [https://support.mozilla.org/en-US/questions/1466444 see] Separate ticket because the call stacks are quite different. openpgp: Cannot decrypt message. decryption.sys.mjs:528:16 openpgp: Decrypted; key=, plainText= decryption.sys.mjs:316:14 openpgp: Extra decryption details: {"encryptedTo":{"myRecipKey":{},"allRecipKeys":[{"keyId":"B8DE03DA7CEA42B2","primaryKeyId":"A9CB8CB214D427B2"},{"keyId":"B8DE03DA7CEA42B2","primaryKeyId":"A9CB8CB214D427B2"}]},"packetDump":":armored input\n :off 0: packet header 0xc1c14c (tag 1, len 524)\n Public-key encrypted session key packet\n version: 3\n key id: 0xb8de03da7cea42b2\n public key algorithm: 1 (RSA (Encrypt or Sign))\n encrypted material:\n rsa m: 4095 bits\n :off 527: packet header 0xc1c14c (tag 1, len 524)\n Public-key encrypted session key packet\n version: 3\n key id: 0xb8de03da7cea42b2\n public key algorithm: 1 (RSA (Encrypt or Sign))\n encrypted material:\n rsa m: 4090 bits\n :off 1054: packet header 0xd2c156 (tag 18, len 534)\n Symmetrically-encrypted integrity protected data packet\n \n "} decryption.sys.mjs:331:16

Alle Antworten (2)

more options

Ugh. No idea how but everything is working. Now there is nothing in the logs about errors; the "GPGME isn't working" does not appear anymore.

My private key has a number UIDs although originally, I couldn't even sign or decrypt with the primary UID, nor with any of the sub UIDs.

I had originally added identities for the sub UIDs under the corresponding accounts where those UIDs can be sent/received. Eventually I discovered that each identity has its own e2ee tab, and specified the same private key ID for each of the identities. Still unsure how that would make signing and decrypt work for the primary UID when it wouldn't before.

Hilfreich?

more options

Perhaps try the encryption list https://thunderbird.topicbox.com/groups/e2ee

Hilfreich?

Stellen Sie eine Frage

Sie müssen sich mit Ihrem Benutzerkonto anmelden, um auf Beiträge zu antworten. Bitte stellen Sie eine neue Frage, wenn Sie noch kein Benutzerkonto haben.