Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
  • H hagrid
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 28
    • Issues 28
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • hagrid-keyserver
  • hagrid
  • Issues
  • #113
Closed
Open
Created Jun 28, 2019 by Daniel Kahn Gillmor@dkgMaintainer

Hagrid should be capable of receiving non-identity updates from the SKS pool

As long as people are adding stuff to the SKS pool, it would be good for hagrid to be able to get those updates. It started with the full dump of the pool, but there is probably some divergence.

Doing this right might require coordinating with at least one SKS maintainer (i'm volunteering) and maybe even getting a patch into SKS to either make sure mailsync works for SKS's recon'ed keys (and then get hagrid to receive updates via mailsync), or to have SKS publish an update log (and then get hagrid to consume that update log somehow).

Assignee
Assign to
Time tracking