Skip to content

Fix DERSignature.stream_serialize length omission - #11

Closed
dgpv wants to merge 1 commit into
Simplexum:masterfrom
m4burns:patch-1
Closed

dgpv wants to merge 1 commit into
Simplexum:masterfrom
m4burns:patch-1

Conversation

@dgpv

@dgpv dgpv commented Oct 18, 2018

Copy link
Copy Markdown

DERSignature.stream_serialize does not write the remaining length of the message after the header byte.

This patch resolves the issue by writing the length of what remains to be written immediately after the header byte.

originally submitted by @m4burns to petertodd#190

DERSignature.stream_serialize does not write the remaining length of the message after the header byte.

This patch resolves the issue by writing the length of what remains to be written immediately after the header byte.
@dgpv

dgpv commented Oct 18, 2018

Copy link
Copy Markdown
Author

Why not use self.length ? it is already calculated and set in stream_deserialize()

@dgpv dgpv closed this Oct 18, 2018
@dgpv

dgpv commented Oct 18, 2018 •

Copy link
Copy Markdown
Author

closing for now. this conversation is better done at the original pull request at python-bitcoinlib: petertodd#190

@dgpv

dgpv commented Dec 11, 2018

Copy link
Copy Markdown
Author

Note that this is now not relevant for python-bitcointx - this code is replaced with a calls to libsecp256k1 functions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants