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

Closed (moved)
Open
Opened Jun 04, 2006 by Roger Dingledine@arma

crypto_global_init(): Initializing OpenSSL via tor_tls_init()

Jun 04 03:01:31.013 [warn] crypto_global_init(): Initializing OpenSSL via tor_tls_init().

We generate this warning on startup, when we follow certain codepaths that reach tor_tls_init before they reach crypto_global_init. For example, if we enable hibernation, then we init_keys before we crypto_global_init.

Is this a bug? If so, we should cause crypto_global_init to be called earlier. If not, we should downgrade the log severity.

[Automatically added by flyspray2trac: Operating System: All]

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