bitcoin

Commit Graph

Author	SHA1	Message	Date
Martin Zumsande	5fc9db504b	test: enable p2p_sendtxrcncl.py with v2transport By adding to the test framework a wait until the v2 handshake is completed, so that p2p_sendtxrcncl.py (which doesn't need to be changed itself) doesnt't send out any other messages before that.	9 months ago
Martin Zumsande	9642aefb81	test: fix intermittent failure in p2p_v2_earlykeyresponse This fixes a possible race between the python NetworkThread and the actual test, which will both call initiate_v2_handshake.	9 months ago
stratospher	bc9283c441	[test] Add functional test to test early key response behaviour in BIP 324 - A node initiates a v2 connection by sending 64 bytes ellswift - In BIP 324 "The responder waits until one byte is received which does not match the V1_PREFIX (16 bytes consisting of the network magic followed by "version\x00\x00\x00\x00\x00".)" - It's possible that the 64 bytes ellswift sent by an initiator starts with a prefix of V1_PREFIX - Example form of 64 bytes ellswift could be: 4 bytes network magic + 60 bytes which aren't prefixed with remaining V1_PREFIX - We test this behaviour: - when responder receives 4 byte network magic -> no response received by initiator - when first mismatch happens -> response received by initiator	10 months ago

Author

SHA1

Message

Date

Martin Zumsande

5fc9db504b

test: enable p2p_sendtxrcncl.py with v2transport

By adding to the test framework a wait until the v2 handshake
is completed, so that p2p_sendtxrcncl.py (which doesn't need
to be changed itself) doesnt't send out any other messages before that.

Martin Zumsande

9642aefb81

test: fix intermittent failure in p2p_v2_earlykeyresponse

This fixes a possible race between the python NetworkThread and the actual
test, which will both call initiate_v2_handshake.

stratospher

bc9283c441

[test] Add functional test to test early key response behaviour in BIP 324

- A node initiates a v2 connection by sending 64 bytes ellswift
- In BIP 324 "The responder waits until one byte is received which does not match the
  V1_PREFIX (16 bytes consisting of the network magic followed by "version\x00\x00\x00\x00\x00".)"
- It's possible that the 64 bytes ellswift sent by an initiator starts with a prefix of V1_PREFIX
- Example form of 64 bytes ellswift could be:
	4 bytes network magic + 60 bytes which aren't prefixed with remaining V1_PREFIX
- We test this behaviour:
	- when responder receives 4 byte network magic -> no response received by initiator
	- when first mismatch happens -> response received by initiator

3 Commits (9ec238d0f3c7b97aec83dbeb4c7a6950c8f5125e)