From: Alfie John <alfie@alfie•wtf>
To: Gregory Maxwell <greg@xiph•org>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP 151 MITM
Date: Thu, 9 Jun 2016 01:42:59 +0000 [thread overview]
Message-ID: <20160609014259.GT32334@dosf1.alfie.wtf> (raw)
In-Reply-To: <CAAS2fgTtu8nqwgrO1u8SRuga6ozcYt7NEDR_tv+cuA3uqgtKvA@mail.gmail.com>
On Thu, Jun 09, 2016 at 01:24:09AM +0000, Gregory Maxwell wrote:
> Reduction to plaintext isn't an interesting attack vector for an active
> attacker: they can simply impersonate the remote side.
>
> This is addressed via authentication, where available, which is done by a
> separate specification that builds on this one.
Are there any links to discussions on how authentication may be done?
Thanks,
Alfie
--
Alfie John
https://www.alfie.wtf
next prev parent reply other threads:[~2016-06-09 1:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 23:47 Alfie John
2016-06-09 1:24 ` Gregory Maxwell
2016-06-09 1:42 ` Alfie John [this message]
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=20160609014259.GT32334@dosf1.alfie.wtf \
--to=alfie@alfie$(echo .)wtf \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=greg@xiph$(echo .)org \
/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