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
  • !575

Closed
Opened Apr 27, 2018 by Grigorii Demidov@gdemidovContributor
  • Report abuse
Report abuse

daemon: client-side & server-side tls session resumption with session tickets

  • Overview 24
  • Commits 11
  • Pipelines 12
  • Changes 6

server-side session resumption support is turned off by default

server-side configuration - net.tls_sticket_salt_string(salt_string)

salt_string - salt string used for session ticket key regeneration

Key regeneration algorithm guarantees that all forked kresd instances will use the same session ticket keys.

session ticket key is regenerated every hour.

Edited May 21, 2018 by Grigorii Demidov
Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Reference: knot/knot-resolver!575
Source branch: tls-client-resumption