Re: msgr2 protocol

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

My understanding is that before the protocol msgr2 begins, each party
already has it's own secrete key, and it's public key has been known by
it's peer, and they have alreay shared the session key that will be used
by encryption/decryption.

The secrete key will be used by signature, and the public key will be
used to identify.

I am not sure about the whole key exchange part, is that done by cephx?


On Sat, Jun 4, 2016 at 1:35 AM, Haomai Wang <haomai@xxxxxxxx> wrote:
> On Sat, Jun 4, 2016 at 1:33 AM, Sage Weil <sweil@xxxxxxxxxx> wrote:
>> On Sat, 4 Jun 2016, Haomai Wang wrote:
>>> On Fri, Jun 3, 2016 at 9:24 PM, Sage Weil <sweil@xxxxxxxxxx> wrote:
>>> > I updated the PR with an additional commit that simplifies the
>>> > confounder.  It seems like we only need the confoudner at teh beginning of
>>> > the session, not for every message, since the signature and encryption
>>> > state is chained from the previous frame.  Is that right?
>>> >
>>> >         https://github.com/ceph/ceph/pull/9461/commits/45766fed1864733c5216a7b50f11cce256338170
>>> >
>>> > Full PR:
>>> >
>>> >         https://github.com/ceph/ceph/pull/9461
>>> >
>>> > --
>>> >
>>> > Also, I just realized that now might be a good time to address the ability
>>> > to multiplex different endpoints (sessions) into the same connection.  We
>>> > could add it later with the msgr feature bits, but it'll probably be
>>> > simpler not to have to support two variants of the protocol.  On the other
>>> > hand, it's a lot more complicated.  :(
>>>
>>> What's the use case? different session shares the same connection? Do
>>> you mean different messenger instance will share the same connection
>>> pool?
>>
>> Many OSD's in the same unix process, sharing the same messenger connection
>> pool, eventually using SPDK/DPDK.
>
> OH, great to push this!
>
>>
>> sage
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux