Consider adding no-export-attributes to gpg export options #1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Context
When fetching a key from the local GPG keyring, we currently use:
Adding
no-export-attributeswould additionally strip User Attributes (photos, etc.) at the GPG level before our programmatic stripping runs.Size comparison (hs@schlittermann.de key)
export-cleanexport-minimalexport-minimal,no-export-attributesTrade-offs
Pro: ~5KB smaller input before programmatic stripping. Less data to parse.
Con: Our
stripKey()already discards User Attributes programmatically (and warns about them). Addingno-export-attributesat the GPG level means those warnings would no longer appear for keyring lookups — the attributes are silently gone before we see them. This could be confusing if a user expects to see what was stripped.Decision needed
Should we add
no-export-attributesto the GPG export options, accept the silent stripping, and potentially lose the warning? Or keep the current behavior where attributes are stripped programmatically with an explicit warning?