Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S sbws
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • 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
  • Network Health
  • sbws
  • Issues
  • #40054
Closed
Open
Issue created Feb 04, 2021 by Georg Koppen@gkOwner

Teach sbws to use SNI or move off of Fastly for bwauth files

Fastly noticed that some of our traffic does not use SNI and they are not happy with that. After some investigation done by @arma and @weasel it turns out that the bulk of the problematic traffic stems from BW Auths fetching files. In particular I think this is due to longclaw's and/or maatuska's bwauth configuration.

The two options we have are moving off of Fastly or support proper SNI. This is somewhat urgent and should happen within the next days.

Assignee
Assign to
Time tracking