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
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

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

Closed (moved)
Open
Opened Oct 24, 2015 by Trac@tracbot

fail self-test for cert_new in v0.2.8.0-alpha-dev NetBSD 6_Stable

Starting in the last 2-5 days, I started getting failed self-test on cert_new as shown: tortls/create_certificate: [forking] OK tortls/cert_new: [forking] [Lost connection!] [cert_new FAILED]

just built 'tor -V' shows: Oct 23 20:41:00.966 [notice] Tor v0.2.8.0-alpha-dev (git-8acaac4622c67ce8) running on NetBSD with Libevent 2.1.5-beta, OpenSSL 1.1.0-dev and Zlib 1.2.3.

NOTE : I'm building against HEAD on OpenSSL 1.1.0-dev ... in case the bug is an OpenSSL regression...

Trac:
Username: yancm

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