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

Closed (moved)
Open
Opened Oct 06, 2015 by Nick Mathewson@nickm🥄

Revise tests in test_tortls.c to not act intrusively on openssl internals

With openssl 1.1, most openssl structures will become opaque. But the new unit tests in test_tortls.c assume that they have full access to openssl internals.

I've wrapped the tests that make this assumption inside #ifndef OPENSSL_OPAQUE, so that Tor will build with openssl 1.1 again. But it would be great to see if we can port some of these tests to work with openssl 1.1, or at least disable the problematic parts on a more fine-grained basis.

To upload designs, you'll need to enable LFS and have an 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#17253