• Members 18 posts
    May 9, 2018, 9:51 a.m.


    I'm using GPG on Mac OS (GPG Suite from gpgtools.org until pEp for iOS and Apple Mail become available) and have a question regarding the compatibility / interoperability of PGP an pEp.

    This is the situation:

    $Person installed pEp for Thunderbird (via Enigmail).
    I wrote a signed Email to $Person which contained my private key.
    $Person answered this Email (= $Response).

    What I would have expected (thinking pEp is fully compatible / interoperable w/ PGP / GPG):

    $Response is encrypted and signed using PGP. and contains the public key of $Person

    What actually happened:

    $Response contained the public key of $Person but was neither signed nor encrypted.

    Do I have a misconception here?

    And on a sidenote: Is there a reason why pEp's public key are "only" 2048 bits long?


  • Members 18 posts
    May 9, 2018, 11:23 a.m.

    $Person can read my encrypted reply.
    When $Person writes to me, the "security amp system" is grey and shows unsecure – Key is not available.

    Seems like Enigmail doesn't import my public key / Signature automatically and pEp users have to import those themselves to encrypt with PGP users?

  • May 10, 2018, 7:17 a.m.

    In the "Enigmail/pEp" menu in Thunderbird on the compatibility tab (2) is a button to show the enigmail logfile, can you provide that?
    What is the filename of the attachment that contains your key?
    Handling Keys and calculating colors are asynchronous tasks. Do follow up e-mails get a color?

  • Members 18 posts
    May 11, 2018, 9:26 a.m.

    I don't use pEp myself (yet) and don't have access to the $Person that does.
    $Person might have tempered with the default settings.
    $Person imported my public key manually. After that, messages to me were encrypted.

    My public key ends with .asc, as well as my signature.

  • May 11, 2018, 9:34 a.m.

    There is an open task for handling RFC2231. So if you use attachments with long names or names that use non-ascii characters, the engine has troubles recognizing it.
    That's why i asked for the exact filename, the extension is secondary to the problem.

  • Members 18 posts
    May 11, 2018, 12:39 p.m.

    I see, sorry.
    The Public Key that GPG Suite exports is named like [First Name] [Last Name] ([KeyID]) – Öffentlich.asc

    Bastian Beuttel (7C34187F) – Öffentlich

  • May 11, 2018, 12:52 p.m.

    looks exactly like our internal test case, which is currently being worked on.
    It should help (for now) if you use "BastianB.asc" or similiar short names with letters/numbers from ascii only. No "ö" , whitespace or thelike

  • Members 18 posts
    May 11, 2018, 1:32 p.m.

    Thanks for the workaround!