public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Maximiliano Sandoval <m.sandoval@proxmox.com>
Cc: Wolfgang Bumiller <w.bumiller@proxmox.com>
Subject: Re: [pve-devel] [PATCH qemu-server] config: add system and service credentials support
Date: Thu, 3 Apr 2025 09:56:02 +0200	[thread overview]
Message-ID: <403c7742-d76c-4472-913f-562f8cb18d53@proxmox.com> (raw)
In-Reply-To: <09b570e5-fce3-4ecc-a898-9400f21d778a@proxmox.com>

Am 03.04.25 um 09:49 schrieb Thomas Lamprecht:
> Am 02.04.25 um 16:36 schrieb Maximiliano Sandoval:
>> Allows to pass system and service credentials to a VM. See [1] for a
>> description of credentials. This can be potentially used to provision a
>> VM as per [2]. Values can be passed either as plain text or as a base64
>> encoded string when the base64 flag is set.
> 
> Would this also make sense for Containers?
> 
> If it's something we can expose for all guests, we could also (later) look
> into implementing some simple registry (like a mappings type) fulfilling
> what the snippets approach would  provide one while having it nicely
> integrated into our access control system.
> 
>>
>> A VM configuration file which, for example, contains:
>>
>>     systemd-cred0: name=foo,value=bar
>>     systemd-cred1: name=encoded-foo,value=YmFy,base64=1
> 
> Tangentially related: Moving the VM config fully over to section config
> parsing would get us list/array support for free – albeit the move might be
> rather costly..
Oh, and one alternative would be to provide just one `systemd-credenentials` key
here that always refers to such a credential mapping, which has then an array
of all the credentials with their name and value.

As I checked [fdo-sc] and there are like 50 supported credentials, some with
a glob to allow sets of credentials per type like for network or udev rules,
so 15 might not cut it quite fast even if the use-case is not _that_ complex.

[fdo-sc] https://www.freedesktop.org/software/systemd/man/latest/systemd.system-credentials.html


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

  reply	other threads:[~2025-04-03  7:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-02 14:36 Maximiliano Sandoval
2025-04-03  7:49 ` Thomas Lamprecht
2025-04-03  7:56   ` Thomas Lamprecht [this message]
2025-04-03  8:48     ` Maximiliano Sandoval
2025-04-03  8:34   ` Maximiliano Sandoval
2025-04-03  9:04     ` Thomas Lamprecht
2025-04-03  9:42       ` Lukas Wagner

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=403c7742-d76c-4472-913f-562f8cb18d53@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=m.sandoval@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=w.bumiller@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