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

Closed (moved)
Open
Opened Jan 25, 2011 by Sebastian Hahn@sebastian

tls context not re-initialized when changing relay/bridge state

This means that a Vidalia-controlled Tor will assert when changing from relay to bridge. Unfortunately, restarting Tor does not help this situation at all, the same assert will happen again (I guess Vidalia realizes that Tor hasn't written its configuration and that it should have a different config, so it applies the change again, and Tor crashes again).

The assert is:

[err] assert_identity_keys_ok(): Bug: router.c:154: assert_identity_keys_ok: Assertion 0!=crypto_pk_cmp_keys(client_identitykey, server_identitykey) failed; aborting.

I think what we need to do here is to make sure we re-initialize our tls context whenever we change our public_server_mode().

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