#243 session key renegotiation is needed

[Aaron Bentley]

This message frequently appears:
DEBUG (PubTracker): [2000-11-22_01:43:05]: WARNING: Couldn't find publication tracker broadcaster

It always happens after
DEBUG (crypto): [2000-11-22_01:42:04]: WARNING: a message arrived with suggested commstrat {'IP address': 'tracker02.mojonation.net', 'comm strategy type': 'TCP', 'open connection': 'true', 'open connection peername': "('64.71.128.169', 253 33)", 'port number': '25333'}, asyncsock: <TCPConnection connected at 84d8420>, peername: ('64.71.128.169', 25333), counterparty_id: <9538>, that couldn't be decrypted. Perhaps it was cleartext, or garbled. The message was '\000\000\000\001u!\254,\257DRU...data total 376 bytes...qu\333\213c\330D\267\335\265"f'. The error was: <Error: no such session>

Version: .920 (upgraded from previous version)
Platform: RH 6.2

Configuration: Block server, content tracker, publishing agent, relay server all enabled.

[Gregory P. Smith]

The "no such session" error is bad. That means that somehow you lost your negotiated shared session key for receiving messages from <9538> (the root metatracker). Since this error is rare and shouldn't be happening we haven't made implementing session key renegotiation a high priority.

The solution for now is to generate a new broker id key. The quick and very dirty was is to remove your config file. The preferred method is to delete the TRANSACTION_MANAGER_STRING line from your broker.conf file. it's in ~/.mojonation/broker/broker.conf on linux, and c:\Program Files\Mojo Nation\config\broker\broker.conf on windows.

I'm lowering the priority of this to 3 but leaving it open as a reminder that we do need session key renegotiation eventually.

[Andrew Archibald]

Logged In: YES
user_id=180731

This is the same as #212396, "crypto keys are fragile".
This situation can easily arise when restoring from backups,
and the quick and dirty solution of deleting your old
identity and generating a new one also obliterates all your
reputation.

See the other bug, but adding renegotiation should not be
difficult.