Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • schleuder schleuder
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 108
    • Issues 108
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • schleuderschleuder
  • schleuderschleuder
  • Issues
  • #395
Closed (moved) (moved)
Open
Issue created Jan 18, 2019 by dkg@dkg

schleuder should properly handle OpenPGP keys with raw e-mail addresses as the User ID

Given a key generated with:

gpg --batch --quick-gen-key 'alice@example.com'

Its user ID doesn't have any angle brackets in it.

If such an OpenPGP certificate gets imported to schleuder, schleuder does some weird things.

For one thing, it doesn't appear to associate that key with any e-mail address.

For another, when you do:

schleuder-cli list list@example.net

then the list duplicates the fingerprint in question on the first line of the output list. So before the import it shows:

6789012345678901234567890123456789012345 subscriber1@example.org
1234567890123456789012345678901234567890 subscriber2@example.biz

and after it shows:

3456789012345678901234567890123456789012 6789012345678901234567890123456789012345 subscriber1@example.org
1234567890123456789012345678901234567890 subscriber2@example.biz

yikes!

These kinds of User IDs are not wide-spread. Autocrypt recommends using <foo@example.org> instead of foo@example.org and #146 also suggests wrapping addresses in angle brackets (<>). But some user IDs like that do exist in the wild, and schleuder should handle them more gracefully.

Assignee
Assign to
Time tracking