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

Closed (moved)
Open
Opened Dec 06, 2019 by Nick Mathewson@nickm🥄

Make tor_tls_get_buffer_sizes() work again

Where supported, Tor uses OpenSSL skulduggery to find out how much RAM openssl has allocated and/or is using for buffers in each SSL object, and . This information is only used for logging right now (in dumpstats()), but it has potential use in our OOM/DOS prevention code.

The tricks that we used up till now no longer actually work with OpenSSL 1.1.0, however, since the relevant structures are now opaque. We'll either need to find another way to get their sizes, or add some API to OpenSSL to expose them.

This is low-priority, unless we actually have time to use this information in OOM calculation.

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