Multisite sync: is metadata transferred in plain text?
Hi, We have a multisite Ceph configuration, with http (not https) sync endpoints. Are all sync traffic in plain text? We have concerns about metadata. For example, when syncing a newly created user and its access key and secret key from the Master zone to a secondary zone, is this traffic in plain text? If so, what are options to encrypt it? Thank you, Mary
Feels like you answered your own question here - why not just use HTTPS for your multisite sync? I'm not aware of any other encryption mechanisms for metadata (I guess using SSE encryption for your data may save that going over in plain text) and would assume that just using HTTP would indeed be a security risk. ________________________________ From: maryzhang0920@gmail.com <maryzhang0920@gmail.com> Sent: Thursday, September 19, 2024 6:01 AM To: ceph-users@ceph.io <ceph-users@ceph.io> Subject: [EXTERNAL] [ceph-users] Multisite sync: is metadata transferred in plain text? Hi, We have a multisite Ceph configuration, with http (not https) sync endpoints. Are all sync traffic in plain text? We have concerns about metadata. For example, when syncing a newly created user and its access key and secret key from the Master zone to a secondary zone, is this traffic in plain text? If so, what are options to encrypt it? Thank you, Mary _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
Thank you Alex. I was hoping session key might be used to encrypt meta data. Thanks, Mary On Mon, Sep 23, 2024, 1:24 AM Alex Hussein-Kershaw (HE/HIM) < alexhus@microsoft.com> wrote:
Feels like you answered your own question here - why not just use HTTPS for your multisite sync?
I'm not aware of any other encryption mechanisms for metadata (I guess using SSE encryption for your data may save that going over in plain text) and would assume that just using HTTP would indeed be a security risk.
------------------------------ *From:* maryzhang0920@gmail.com <maryzhang0920@gmail.com> *Sent:* Thursday, September 19, 2024 6:01 AM *To:* ceph-users@ceph.io <ceph-users@ceph.io> *Subject:* [EXTERNAL] [ceph-users] Multisite sync: is metadata transferred in plain text?
Hi,
We have a multisite Ceph configuration, with http (not https) sync endpoints. Are all sync traffic in plain text? We have concerns about metadata. For example, when syncing a newly created user and its access key and secret key from the Master zone to a secondary zone, is this traffic in plain text? If so, what are options to encrypt it?
Thank you, Mary _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
We have a multisite Ceph configuration, with http (not https) sync endpoints. Are all sync traffic in plain text?
For S3 v4 auth, there are things that "obfuscates" the login auth, but might not be called real crypto in that sense, so if you decide to send things in the clear, expect it to be sent in the clear, even if it is made "hard to read".
We have concerns about metadata. For example, when syncing a newly created user and its access key and secret key from the Master zone to a secondary zone, is this traffic in plain text? If so, what are options to encrypt it?
Then either choose https or wrap your traffic in any of the VPN solutions from the last 30 years or so. If the endpoints can't be changed to https for some reason, then secure all the traffic just like with any other communication protocol. -- May the most significant bit of your life be positive.
Got it, thank you Janne. Best Regards, Mary On Mon, Sep 23, 2024, 1:30 AM Janne Johansson <icepic.dz@gmail.com> wrote:
We have a multisite Ceph configuration, with http (not https) sync endpoints. Are all sync traffic in plain text?
For S3 v4 auth, there are things that "obfuscates" the login auth, but might not be called real crypto in that sense, so if you decide to send things in the clear, expect it to be sent in the clear, even if it is made "hard to read".
We have concerns about metadata. For example, when syncing a newly created user and its access key and secret key from the Master zone to a secondary zone, is this traffic in plain text? If so, what are options to encrypt it?
Then either choose https or wrap your traffic in any of the VPN solutions from the last 30 years or so. If the endpoints can't be changed to https for some reason, then secure all the traffic just like with any other communication protocol.
-- May the most significant bit of your life be positive.
participants (4)
-
Alex Hussein-Kershaw (HE/HIM)
-
Janne Johansson
-
Mary Zhang
-
maryzhang0920＠gmail.com