Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #9774

Closed (moved)
Open
Opened Sep 19, 2013 by Roger Dingledine@arma

Explain "#ifdef CURVE25519_ENABLED" better

I find the CURVE25519_ENABLED ifdefs really confusing. It would seem to mean "can we do ntor handshakes", but if it does, why is there a bunch of ntor code not covered by ifdefs? When should I check ifdef when doing something ntor-related, and when shouldn't I? Are there things that aren't ntor-related where it matters?

I was about to send Nick mail asking, but then I realized that other / future Tor developers should want to know the answer too.

Thanks!

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Tor: 0.2.5.x-final
Milestone
Tor: 0.2.5.x-final
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#9774