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

Closed (moved)
Open
Opened Mar 16, 2012 by Nick Mathewson@nickm🥄

Use EVP_aes_128_ctr() on OpenSSL >= 1.0.1

Starting with OpenSSL 1.0.1, there is an EVP value to provide counter-mode AES. We definitely want to be using this one for our counter mode implementation in aes.c, since it appears to automatically use the best available AES implementation, including tricky ones that use AESNI/bitsliced/vectorized implementations.

Bitsliced and vectorized implementations of counter mode are not only faster than the straightforward assembly versions, but also run in constant-time.

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