[tor-bugs] #2433 [- Select a component]: tls context not re-initialized when changing relay/bridge state
Tor Bug Tracker & Wiki
torproject-admin at torproject.org
Tue Jan 25 12:35:05 UTC 2011
#2433: tls context not re-initialized when changing relay/bridge state
----------------------------------+-----------------------------------------
Reporter: Sebastian | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: - Select a component | Version:
Keywords: | Parent:
----------------------------------+-----------------------------------------
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().
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/2433>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list