Bitmessage/PyBitmessage-2024-08-21
Archived
2
0
Fork 0
Code Issues 168 Pull Requests 53 Actions Packages Projects Releases 5 Wiki Activity

Correct articles in the verack section of the Spec, emphasize must uniformly

Browse Source
This commit is contained in:
Lee Miller 2023-10-03 16:24:54 +03:00
parent 7c62936820
commit 427965cac3
Signed by untrusted user: lee.miller
GPG Key ID: 4F97A5EA88F4AB63
1 changed files with 8 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
docs/protocol.rst
View File

@ -92,7 +92,7 @@ Variable length integer
Integer can be encoded depending on the represented value to save space.
Variable length integers always precede an array/vector of a type of data that
may vary in length. Varints MUST use the minimum possible number of bytes to
may vary in length. Varints **must** use the minimum possible number of bytes to
encode a value. For example, the value 6 can be encoded with one byte therefore
a varint that uses three bytes to encode the value 6 is malformed and the
decoding task must be aborted.
@ -480,12 +480,13 @@ only a :ref:`message header <Message structure>` with the command string
"verack". The TCP timeout starts out at 20 seconds; after verack messages are
exchanged, the timeout is raised to 10 minutes.
If both sides announce that they support SSL, they MUST perform a SSL handshake
immediately after they both send and receive verack. During this SSL handshake,
the TCP client acts as a SSL client, and the TCP server acts as a SSL server.
The current implementation (v0.5.4 or later) requires the AECDH-AES256-SHA
cipher over TLSv1 protocol, and prefers the secp256k1 curve (but other curves
may be accepted, depending on the version of python and OpenSSL used).
If both sides announce that they support SSL, they **must** perform an SSL
handshake immediately after they both send and receive verack. During this SSL
handshake, the TCP client acts as an SSL client, and the TCP server acts as an
SSL server. The current implementation (v0.5.4 or later) requires the
AECDH-AES256-SHA cipher over TLSv1 protocol, and prefers the secp256k1 curve
(but other curves may be accepted, depending on the version of python and
OpenSSL used).
addr
^^^^