Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S Snowflake
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 70
    • Issues 70
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 6
    • Merge requests 6
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Anti-censorship
  • Pluggable Transports
  • Snowflake
  • Issues
  • #30512

Closed
Open
Created May 14, 2019 by David Fifield@dcfOwner

Enable cache for ACME certificates in broker

The websocket server caches its automatic certificates: https://gitweb.torproject.org/pluggable-transports/snowflake.git/tree/server/server.go?id=d865b7c252d3a7efd789a84757fc2635b1964921#n309 But the broker does not: https://gitweb.torproject.org/pluggable-transports/snowflake.git/tree/broker/broker.go?id=d865b7c252d3a7efd789a84757fc2635b1964921#n265

In legacy/trac#30509 (moved) the broker exceeded the Let's Encrypt rate limits and couldn't get a new certificate. Implementing a certificate cache will prevent it from happening again.

Once implemented, remember to undo the temporary --cert and --key configuration that was set up in comment:6:ticket:30509. That certificate is good for 1 year.

Assignee
Assign to
Time tracking