Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
schleuder
schleuder
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 99
    • Issues 99
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • schleuder
  • schleuderschleuder
  • Issues
  • #489

Closed
Open
Created Mar 07, 2021 by lu x@lux

Feature Request: (Add option to) publish list-key to web key directory

Problem:

Since many mailclients are moving from SKS to verified keyservers and WKD, it has become rather cumbersome to publish a whole list key.

For example, when publishing a key to keys.openpgp.org, you would need to verify the identity for its sub-identites too (list-request or list-owner), and for an encrypted-only list you would need to fish the verification link out of the attachment of the bounce-notification

(I am aware that you can write to list-sendkey for the public key, but many schleuder users are either not aware or generally alienated by the idea of managing a subscription via mail commands)

Solution

It would be great if schleuder could publish it's list keys via web key directory. GnuPG >= 2.2.14 includes a web key service, so this might be possible without adding additional dependencies to schleuder.

I do not know ruby (yet) and my programming experience is almost none, but if you approve the idea I could a look at the codebase and see if I can do a contribution (..and maybe you already know a convenient way to do this and can point me to the direction 😄 )

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None