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

Closed (moved)
(moved)
Open
Created May 19, 2011 by Damian Johnson@atagar

Setting BridgeRelay Triggers Assertion Failure

Hi, with the current git checkout... Tor v0.2.2.27-beta (git-e3b8457eb38ee76a)

And also back at: Tor v0.2.2.23-alpha (git-b85eb949b528f4d7)

running "SETCONF BridgeRelay=1" triggers an assertion failure and Tor crash: May 18 20:42:13.855 [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. router.c:154 assert_identity_keys_ok: Assertion 0!=crypto_pk_cmp_keys(client_identitykey, server_identitykey) failed; aborting. Aborted

Assertion Source: https://gitweb.torproject.org/tor.git/blob/HEAD:/src/or/router.c#l154

My torrc before the crash:

ORPort 9001
Nickname armTest
ExitPolicy reject *:* 

ControlPort 9051
CookieAuthentication 1

AccountingMax 100 GB

Cheers! -Damian

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