From: Tamas Blummer <tamas@bitsofproof•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] var_int ambiguous serialization consequences
Date: Sun, 1 Feb 2015 10:33:48 +0100 [thread overview]
Message-ID: <D89EBAA3-ED78-4D9C-B693-FBBF27501938@bitsofproof.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1065 bytes --]
I wonder of consequences if var_int is used in its longer than necessary forms (e.g encoding 1 as 0xfd0100 instead of 0x01)
This is already of interest if applying size limit to a block, since transaction count is var_int but is not part of the hashed header or the merkle tree.
It could also be used to create variants of the same transaction message by altered representation of txIn and txout counts, that would remain valid provided signatures validate with the shortest form, as that is created while re-serializing for signature hashing. An implementation that holds mempool by raw message hashes could be tricked to believe that a modified encoded version of the same transaction is a real double spend. One could also mine a valid block with transactions that have a different hash if regularly parsed and re-serialized. An SPV client could be confused by such a transaction as it was present in the merkle tree proof with a different hash than it gets for the tx with its own serialization or from the raw message.
Tamas Blummer
Bits of Proof
[-- Attachment #1.2: Type: text/html, Size: 2410 bytes --]
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 496 bytes --]
next reply other threads:[~2015-02-01 9:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-01 9:33 Tamas Blummer [this message]
2015-02-01 10:44 ` Wladimir
2015-02-01 11:42 ` Tamas Blummer
2015-02-01 15:00 ` Pieter Wuille
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D89EBAA3-ED78-4D9C-B693-FBBF27501938@bitsofproof.com \
--to=tamas@bitsofproof$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox