From: Arthur Gervais <arthur.gervais@inf.ethz.ch>
To: <bitcoin-development@lists.sourceforge.net>
Cc: Ghassan Karame <ghassan@karame.org>,
Hubert Ritzdorf <rihubert@inf.ethz.ch>
Subject: [Bitcoin-development] Double-Spending Fast Payments in Bitcoin due to Client versions 0.8.1
Date: Thu, 27 Jun 2013 12:23:34 +0200 [thread overview]
Message-ID: <51CC12A6.3090100@inf.ethz.ch> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dear Bitcoin developers,
We would like to report a vulnerability which might lead, under some
assumptions, to a double-spending attack in a fast payment scenario.
The vulnerability has been introduced due to signature encoding
incompatibilities between versions 0.8.2 (or 0.8.3) and earlier
Bitcoin versions.
Please find at the following link a detailed description of this
vulnerability:
ftp://ftp.inf.ethz.ch/pub/publications/tech-reports/7xx/789.pdf
We contacted and informed Gavin earlier about this problem.
With best regards,
Arthur Gervais
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: GPGTools - http://gpgtools.org
iQEcBAEBAgAGBQJRzBKLAAoJEI2AYXeasI8/eNYH/2b45o8JPjuiOXeE0MgiYO4g
HgGorNBvH3hLlSZkGh/7GxeGWi3tiEq8DKAgqFd8p+1Ay4YVHK86jJMBxAc8lzpx
TqS6Szrhlx7slamMGhjeem4BJ2RmfVqSRQjidYxwdee8bMQRVH5DiBzndpZwCeHa
AvlP8ojTUFozOJs5PvjEqE+sDKDe5nDC96uiZyMROK8neoiLZpJzV3+ScTUjLCeB
zg34wttX80WKpkXJFvq88FTIvO5E42NGP3APnt2J/HZcey4Mi9UIhLt+/TJ7Z07l
HuxFlzyXdCgRkJWvU13yn8bUP0cbeoox6Cwn7rDAIisVLn4KB9XPThPjfJbKEkg=
=Y6bs
-----END PGP SIGNATURE-----
next reply other threads:[~2013-06-27 10:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 10:23 Arthur Gervais [this message]
2013-06-27 11:04 ` [Bitcoin-development] Double-Spending Fast Payments in Bitcoin due to Client versions 0.8.1 Gregory Maxwell
2013-06-27 16:03 ` Arthur Gervais
2013-06-27 16:13 ` Gregory Maxwell
2013-06-27 16:16 ` Jeff Garzik
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=51CC12A6.3090100@inf.ethz.ch \
--to=arthur.gervais@inf.ethz.ch \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=ghassan@karame.org \
--cc=rihubert@inf.ethz.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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