Skip to content

GitLab

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

Closed
Opened Nov 13, 2016 by Daniel Kahn Gillmor@dkgGuest
  • Report abuse
Report abuse

Create and use ephemeral TLS credentials if none are explicitly configured

  • Overview 2
  • Commits 4
  • Changes 7

If the admin asks kresd to listen using TLS, but they haven't given any credentials, we should just create some credentials and try to serve them up.

This makes it much easier to get dns-over-tls working in opportunistic mode immediately (with no configuration needed), and admins can take the next step (with proper persistent credentials) when they have those logistics worked out.

Assignee
Assign to
Reviewer
Request review from
1.2.0 release
Milestone
1.2.0 release (Past due)
Assign milestone
Time tracking
Reference: knot/knot-resolver!73
Source branch: ephemeral-tls-2