From: Alfie John <alfie@alfie.wtf>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] BIP 151 MITM
Date: Wed, 8 Jun 2016 23:47:28 +0000 [thread overview]
Message-ID: <20160608234728.GQ32334@dosf1.alfie.wtf> (raw)
Hi folks,
Overall I think BIP 151 is a good idea. However unless I'm mistaken, what's to
prevent someone between peers to suppress the initial 'encinit' message during
negotiation, causing both to fallback to plaintext?
Peers should negotiate a secure channel from the outset or backout entirely
with no option of falling back. This can be indicated loudly by the daemon
listening on an entirely new port.
Alfie
--
Alfie John
https://www.alfie.wtf
next reply other threads:[~2016-06-08 23:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 23:47 Alfie John [this message]
2016-06-09 1:24 ` [bitcoin-dev] BIP 151 MITM Gregory Maxwell
2016-06-09 1:42 ` Alfie John
2016-06-09 6:57 ` Jonas Schnelli
2016-06-09 7:00 ` Alfie John
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=20160608234728.GQ32334@dosf1.alfie.wtf \
--to=alfie@alfie.wtf \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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