Details
-
Bug
-
Status: Complete
-
High
-
Resolution: Invalid
-
None
-
None
-
None
Description
The test test_new_node_catchup_update_projection generate the following message:
2017-06-22 17:59:35,988 | INFO | node.py (1170) | handleOneNodeMsg | Theta msg validated ({'request': {'reqId': 1498143567022608, 'operation': {'type': '1', 'verkey': '~V58citHknD8gdJqiXEHGQe', 'dest': '5JVfBVWLKvMiEL1JFC6LT5', 'role': '101'}, 'identifier': 'BPtrqHo3WyjmTNpVchEhWxp3qfDdssdFUNoM8kmKoEWw', 'signature': '3XBw87qoFX86RWoBTXu3rAitFta2imwqf9JUw4sJcMmCY5RE3UamkhHHVkG8STFJPVzrR3HijCib1YNXGLHB5oTo'}, 'senderClient': 'L-.wJiB4N{(8[Bxb?:ZboQS?6Q4s+yPXLnTa>Zsq'}, b'OJSTO>6%Ytu@@zuWh>08?F@>}fK:=XD+Ygg8)z{A')
The message has format:
({'senderClient': <client_id>, 'request': <client request>}, <from>)
from is a name of the sender who has sent the message.
In the example above node Theta gets message from node with name:
b'OJSTO>6%Ytu@@zuWh>08?F@>}fK:=XD+Ygg8)z{A'
Later, Theta prints:
2017-06-22 17:59:35,996 | WARNING | node.py (2122) | reportSuspiciousNode | Theta raised suspicion on node OJSTO for could not authenticate; suspicion code is 110
I suspect an error in the test or code either.
I have to add a workaround in https://github.com/evernym/plenum/pull/224/commits/2650afca2efa185f00f76350470e48039afc5e46#diff-b490c747b8f70e0c134e3cd446406b48R31.
Please, take care about the workaround (remove or allow byte names).