public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: Kefu Chai <k.chai@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [PATCH manager] ceph: create service and bootstrap keyrings with mode 0600
Date: Mon, 12 Oct 2026 14:17:37 +0200	[thread overview]
Message-ID: <s8owlrn5d0e.fsf@toolbox> (raw)
In-Reply-To: <20261012104642.1046894-1-k.chai@proxmox.com> (Kefu Chai's message of "Mon, 12 Oct 2026 18:46:42 +0800")

Kefu Chai <k.chai@proxmox.com> writes:

> The keyrings for a new MDS, manager and client.bootstrap-osd are
> written without a mode and end up 0644. Whoever reads one gets that
> entity's caps: the MDS and manager keys can read and write every pool,
> the bootstrap key can register OSDs. Only the 0750 /var/lib/ceph keeps
> other users out.
>
> ceph-mon --mkfs was changed to 0600 for the same reason (Ceph tracker
> #14950), and ceph-authtool, cephadm and the cephx migration helper all
> write keyrings as 0600.
>
> The daemons own their keyrings after the chown, and ceph-volume reads
> the bootstrap keyring as root, so nothing loses access. Existing
> keyrings are not changed.
>
> Link: https://tracker.ceph.com/issues/14950
> Signed-off-by: Kefu Chai <k.chai@proxmox.com>


Tested

pveceph $service destroy
pveceph $service create

for OSD, MGR, and MDS on a cluster where they were created with 0644.
Recreating the services sets the permission to 600 and worked as
expected.

This came up at Enterprise support ticket #0706190.

Tested-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
Reviewed-by: Maximiliano Sandoval <m.sandoval@proxmox.com>


-- 
Maximiliano




      reply	other threads:[~2026-10-12 12:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-12 10:46 [PATCH manager] ceph: create service and bootstrap keyrings with mode 0600 Kefu Chai
2026-10-12 12:17 ` Maximiliano Sandoval [this message]

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=s8owlrn5d0e.fsf@toolbox \
    --to=m.sandoval@proxmox.com \
    --cc=k.chai@proxmox.com \
    --cc=pve-devel@lists.proxmox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal