From: Sage Weil <sage@newdream.net>
To: Marcus Watts <mwatts@redhat.com>
Cc: Haomai Wang <haomai@xsky.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: msgr2 protocol
Date: Fri, 27 May 2016 13:33:12 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.11.1605271330580.4873@cpach.fuggernut.com> (raw)
In-Reply-To: <20160527082833.GB24096@degu.eng.arb.redhat.com>
On Fri, 27 May 2016, Marcus Watts wrote:
> Of course you still need to somehow protect against a "downgrade" MITM
> attack.
How is this generally done? I'm thinking about, for example, a MITM who
silently drops the TAG_ENCRYPT message in the protocol I described. It
seems like we need a secure TAG_AUTH_something that makes a statement
about what has been negotiated before we start the message exchange or
else some part of the initial exchange could have been dropped.
?
sage
next prev parent reply other threads:[~2016-05-27 17:32 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 18:17 msgr2 protocol Sage Weil
2016-05-27 4:41 ` Haomai Wang
2016-05-27 4:45 ` Haomai Wang
2016-05-27 8:28 ` Marcus Watts
2016-05-27 17:33 ` Sage Weil [this message]
2016-05-27 17:28 ` Sage Weil
2016-05-27 9:44 ` Yehuda Sadeh-Weinraub
2016-05-27 17:37 ` Sage Weil
2016-05-28 18:19 ` Yehuda Sadeh-Weinraub
2016-06-02 15:43 ` Sage Weil
2016-06-02 15:59 ` Haomai Wang
2016-06-02 16:35 ` Sage Weil
2016-06-02 18:11 ` Gregory Farnum
2016-06-02 18:24 ` Sage Weil
2016-06-02 18:34 ` Gregory Farnum
2016-06-03 13:11 ` Sage Weil
2016-06-03 13:24 ` Sage Weil
2016-06-03 16:47 ` Haomai Wang
2016-06-03 17:33 ` Sage Weil
2016-06-03 17:35 ` Haomai Wang
2016-06-06 8:23 ` Junwang Zhao
2016-06-10 8:31 ` Marcus Watts
2016-06-10 10:11 ` Sage Weil
2016-06-10 10:48 ` Sage Weil
2016-06-06 20:16 ` Gregory Farnum
2016-06-10 11:04 ` Sage Weil
2016-06-10 19:05 ` Marcus Watts
2016-06-10 21:15 ` Sage Weil
2016-06-10 21:22 ` Gregory Farnum
2016-06-11 23:05 ` Marcus Watts
2016-06-12 23:59 ` Sage Weil
[not found] ` <CACJqLyax_SXEZp3vA2_wR+CdwKOo2Re=SsK2xfXqmXjz9d8iNw@mail.gmail.com>
2016-09-09 21:14 ` Sage Weil
[not found] ` <CACJqLyYwKZ5_1OHR_5=+mr=1ED2Nt34x4TB29j5dE1D+NjzFpg@mail.gmail.com>
2016-09-10 14:43 ` Haomai Wang
2016-09-11 17:05 ` Sage Weil
2016-09-12 2:29 ` Haomai Wang
2016-09-12 13:21 ` Sage Weil
2016-09-13 0:03 ` Gregory Farnum
2016-09-13 1:35 ` Haomai Wang
2016-09-13 13:21 ` Sage Weil
2016-09-13 11:50 ` Jeff Layton
2016-09-13 11:18 ` Jeff Layton
2016-09-13 13:31 ` Sage Weil
2016-09-13 14:48 ` Jeff Layton
2016-09-13 15:10 ` Sage Weil
2016-09-13 20:07 ` Gregory Farnum
2016-06-02 18:16 ` Gregory Farnum
2016-06-29 11:59 Avner Ben Hanoch
2016-06-29 16:52 ` Yehuda Sadeh-Weinraub
2016-06-30 11:59 ` Avner Ben Hanoch
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=alpine.DEB.2.11.1605271330580.4873@cpach.fuggernut.com \
--to=sage@newdream.net \
--cc=ceph-devel@vger.kernel.org \
--cc=haomai@xsky.com \
--cc=mwatts@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.