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

Closed (moved)
(moved)
Open
Created Nov 03, 2016 by Nick Mathewson@nickm🍬

Memory leak in crypto_write_public_key_to_string() with OpenSSL master

The expensive-hardening version of the tests had a memory leak when we were encoding public keys. The fix is easy -- I don't know why we programmed it the way we did in the first place.

Found on https://jenkins.torproject.org/job/tor-ci-linux-master-expensive-hardening/ARCHITECTURE=amd64,SUITE=sid/425/consoleFull -- so is that openssl 1.1 too?

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