Proper parsing of secret keys

Issue #90 resolved
Anonymous created an issue

Secret keys are not properly parsed using GNUPG 2.2. This seems to be caused by changes in output of GNUPG itself (see https://dev.gnupg.org/T3431).

This is a reiteration of #86.

Comments (4)

  1. Vinay Sajip repo owner

    There's no need to create a separate issue for this, you could just open #86/mark as enhancement when GnuPG provides a mechanism for correctly determining whether the key is private or public.

    Depending on GnuPG's fix, it may be that python-gnupg will work without any changes (as it does on older GnuPG versions).

  2. Log in to comment