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
  • #9667

Closed (moved)
(moved)
Open
Created Sep 04, 2013 by Nick Mathewson@nickm🍬

Consider batch-exponentiation tricks to improve ntor performance

In the ntor paper, the authors say:

In our protocol the server needs to compute X^b^ and X^y^. Since the base is the same, squarings in the squareand-multiply algorithm can be parallelized [MN96] reducing the computational cost to 1.33 exponentiations. Further improvements such the \Exponent Combination Method" [MN96, x2.3] can be applied to the computation of the server. However such algorithms further increase the complexity of the computations and the improvements are not always clear cut.

This is why they list "1.33" online exponentiations, while our naive implementation has 2.

We should examine whether we can actually use some/all of these techniques. (I believe there has been some discussion on the point on tor-dev already; anybody want to dig up a link?)

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