Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature SubPacket options removed when using keys generated with GnuPG 2.3.8+ #468

Open
arthurvanduynhoven opened this issue Aug 20, 2024 · 0 comments

Comments

@arthurvanduynhoven
Copy link

As of GnuPG 2.3.8 the features subpacket section 30 (under signature packet) is now always adding the reserved flags. Since PGPy does not recognize these flags it removes them and alters the key value making the key unusable later with GnuPG.

Reproduction steps:

  1. Install GnuPG 2.3.8+
  2. Create new key gpg --expert --full-generate-key
  3. Export key gpg --armor --output test-key-2.3.8.asc --export <key id here>
  4. Import key using PGPy my_key = pgpy.PGPKey.from_file(test-key-2.3.8.asc)
  5. Print public key using PGPy str(my_key.pubkey)
  6. Original value is different than the printed public key using PGPy str(my_key.pubkey) != test-key-2.3.8.asc
  7. Try to import the printed key into GnuPG from PGPy and unable.
arthurvanduynhoven added a commit to arthurvanduynhoven/PGPy that referenced this issue Aug 20, 2024
…ures flag options

Signed-off-by: Arthur Van Duynhoven <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant