Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 823
    • Issues 823
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 30
    • Merge requests 30
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #2433
Closed
Open
Created 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
Time tracking