From: Iztok Gregori <iztok.gregori@elettra.eu>
To: pve-user@lists.proxmox.com
Subject: Puppet/Openvox and ssh authorized_keys file
Date: Wed, 9 Sep 2026 12:30:02 +0200 [thread overview]
Message-ID: <1294fddd-69a3-4fc8-841b-5ece917ca7e6@elettra.eu> (raw)
Hi to all!
I have some specific questions regarding how Proxmox handles
authorized_keys file and how to manage that file with puppet/openvox.
- When the "/etc/pve/priv/authorized_keys" is created/updated by
Proxmox? I suspect on the cluster creation and after a node is
added/removed, but I'm not certain.
- If is a regular file or is missing, when the symbolic link
"/root/.ssh/authorized_keys" (which points to
"/etc/pve/priv/authorized_key") is recreated? At node startup?
- Is it safe to let openvox/puppet manage directly
"/etc/pve/priv/authorized_keys" (so we can automatically add/remove
administrator ssh keys as needed)?
Thank you for your time
Iztok Gregori
--
Iztok Gregori
ICT Systems and Services
Elettra - Sincrotrone Trieste S.C.p.A.
http://www.elettra.eu
reply other threads:[~2026-09-09 10:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1294fddd-69a3-4fc8-841b-5ece917ca7e6@elettra.eu \
--to=iztok.gregori@elettra.eu \
--cc=pve-user@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