Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #18638

Closed (moved)
(moved)
Open
Created Mar 25, 2016 by Nick Mathewson@nickm🍬

Write a proposal for PK handshake that uses more client resources than server.

Our current handshakes (TLS, TAP, ntor, and ) all have resource asymmetries: a client can send junk with very little effort, and thereby cause a server to spend more CPU. We could instead look for ways to make sure that a client cannot force servers to spend X resources without themselves spending something in vicinity of X resources.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking