Furlong

It seems like we found the error: https://pep.community/t/send-button-of-emails-not-working-anymore-in-pep-mode/39/#post-141 For a quick workaround: Just move all the backup files counting up to gpg.conf.98.pep.bkp from /home/yourname/.gnupg to a subfolder. A real fix will follow from the pEp developers, I guess.

Meanwhile there is a thread at the pEp-Community-Forum: https://pep.community/t/send-button-of-emails-not-working-anymore-in-pep-mode/39/

Same problem here with the forced pEp mode ... it occurred out of nothing pEpAdapter.getIdentitiesForEmails: ERROR: {"code":"PEP-unavailable","exception":null,"message":"Cannot establish connection to PEP service"} Solved it by switching back to Enigmail/SMIME until the pEp people fix it.

Same problem here with the forced pEp mode ... it occurred out of nothing pEpAdapter.getIdentitiesForEmails: ERROR: {"code":"PEP-unavailable","exception":null,"message":"Cannot establish connection to PEP service"} Solved it by switching back to Enigmail/SMIME until the pEp people fix it.

Same problem here with the forced pEp mode ... pEpAdapter.getIdentitiesForEmails: ERROR: {"code":"PEP-unavailable","exception":null,"message":"Cannot establish connection to PEP service"} Solved it by switching back to Enigmail/SMIME until the pEp people fix it.

Thanks for the insight, but I'm still not sure if you are right in all points: 1.) The draft states: "Passphrases to protect a user's private key MUST be supported by pEp implementations, but SHALL NOT be enforced by default. That is, if a pEp implementation finds a suitable (i.e., secure enough) cryptographic setup, which uses passphrases, pEp implementations MUST provide a way to unlock the key." https://tools.ietf.org/html/draft-birk-pep-02#section-5.3 So, passphrase should work. It did indeed...

I had some trouble using my existing private keys together with the pEp-engine - it kept generating new keys directly after I enforced pep mode. Finally I solved it. Here are some hints if someone has similar problems: 1.) pEp seems to have trouble with some keys having passphrases. So it will generate new keys. Solution: Remove the passphrase from your keys: gpg --edit-key FINGERPRINTOFTHEKEY passwd When GnuPG prompts for the new passphrase, just hit enter. Unfortunately, I wasn't able to remove...

I had some trouble using my existing private keys together with the pEp-engine - it kept generating new keys directly after I enforced pep mode. Finally I solved it. Here are some hints if someone has similar problems: 1.) pEp is not at all able to work with multiple instances/profiles of thunderbird running at the same time. While encrypting an email it asks for the passphrase of a totally different key and then sends the email unencrypted. Solution: Integrate all you email accounts into one profile....