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 102
    • Issues 102
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • 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
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • schleuder
  • schleuderschleuder
  • Issues
  • #361

Closed
Open
Opened Jul 16, 2018 by paz@pazOwner

Speak to keyservers directly and drop dirmngr

We were discussion to maybe speak to keyservers directly, via HTTPS.

Pro:

  • We can get rid of a lot of shell-calls,
  • it it much easier and probably much more realiable to test, sks-mock.rb and repeatingly killing dirmngr could probably be dropped,
  • we still can support multiple, specific keyservers,
  • we have much more control over the requests, e.g. can retry in case of timeouts.

Contra:

  • We can not support keyserver-pools (because they don't use proper HTTPS-certificates),
  • we must use a hardcoded default, can't fall back to a system-wide configured keyserver,
  • supporting connections via TOR requires additional work (but not that much: https://rubygems.org/gems/socksify, https://stackoverflow.com/questions/13353544/ruby-tor-and-nethttpproxy/13882749#13882749)
Edited Apr 02, 2019 by georg
Assignee
Assign to
4.0
Milestone
4.0
Assign milestone
Time tracking
None
Due date
None
Reference: schleuder/schleuder#361