搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

OpenPGP does not work after migration from Enigmail

  • 1 回覆
  • 1 有這個問題
  • 2 次檢視
  • 最近回覆由 Andrw

more options

The first indication that something in the new TB 78 did not work as in the TB68+Enigmail was that I could not send from an account gz0001 (in the gmails) to my main account gunter.zielke. It just gave me the error that it could not send it without any further explanation on why. I filed a bug report but could not help to investigate some more. I have published my public key on my website for others to be able to reach me encrypted gunterzielke.com/public-key/ and I noticed that the public key exported from TB78 OpenPGP was different:


BEGIN PGP PUBLIC KEY BLOCK-----

xsFNBFTfzXQBEADfquwFDgWUMmf8sCX7ikG2++vQGO2FQ5hmjrDvoNsxMVh70SNplyQThW3+aByG TJoUDfr84UmVFtNqyjWcbt0Q5Wc93yN93qEepyetkvAZ4FVKS8Dq3Rj0WX47UGOvH6q1souxhoYb .... I dug a bit further and found that also the private keys (for the same email) when exported from TB78 OpenPGP and Kleopatra were totally different. It could well be that my understanding of public-key encryption is insufficient, for example, that there could very well be two different looking public keys from GnuPG and OpenPGP still mean the same thing, so maybe somebody here might be able to give me some insight to reduce my ignorance or help me understand what's going on and why the migrated Enigmail keys don't seem to work in TB OpenPGP. Thank you so much - Gunter

The first indication that something in the new TB 78 did not work as in the TB68+Enigmail was that I could not send from an account gz0001 (in the gmails) to my main account gunter.zielke. It just gave me the error that it could not send it without any further explanation on why. I filed a bug report but could not help to investigate some more. I have published my public key on my website for others to be able to reach me encrypted gunterzielke.com/public-key/ and I noticed that the public key exported from TB78 OpenPGP was different: -----BEGIN PGP PUBLIC KEY BLOCK----- xsFNBFTfzXQBEADfquwFDgWUMmf8sCX7ikG2++vQGO2FQ5hmjrDvoNsxMVh70SNplyQThW3+aByG TJoUDfr84UmVFtNqyjWcbt0Q5Wc93yN93qEepyetkvAZ4FVKS8Dq3Rj0WX47UGOvH6q1souxhoYb .... I dug a bit further and found that also the private keys (for the same email) when exported from TB78 OpenPGP and Kleopatra were totally different. It could well be that my understanding of public-key encryption is insufficient, for example, that there could very well be two different looking public keys from GnuPG and OpenPGP still mean the same thing, so maybe somebody here might be able to give me some insight to reduce my ignorance or help me understand what's going on and why the migrated Enigmail keys don't seem to work in TB OpenPGP. Thank you so much - Gunter

所有回覆 (1)

more options

Same here. TB was auto updated to v78 and my PGP now brocken!

1. Migration from Enigmail was completed succesfull. 2. Tried to configure from scratch.

PGP information from encrypted messages: > Message Cannot Be Decrypted > There are unknown problems with this encrypted message.