From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
	by lore.proxmox.com (Postfix) with ESMTPS id A689C1FF173
	for <inbox@lore.proxmox.com>; Mon, 24 Mar 2025 11:06:46 +0100 (CET)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
	by firstgate.proxmox.com (Proxmox) with ESMTP id 58B36FA73;
	Mon, 24 Mar 2025 11:06:36 +0100 (CET)
Authentication-Results: garm.ovh; auth=pass
 (GARM-96R001ee3a9d8d-b062-4e71-8c6d-b7481e47c872,
 176156A4C8488F3F0BE2024925491AE330929FC1) smtp.auth=simon@sinux.sh
X-OVh-ClientIp: 82.64.45.19
From: Simon LEONARD <git-1001af4@sinux.sh>
To: f.gruenbichler@proxmox.com
Date: Sat, 22 Mar 2025 19:05:58 +0100
Message-ID: <20250322180647.12941-1-git-1001af4@sinux.sh>
X-Mailer: git-send-email 2.49.0
In-Reply-To: <1737975711.7o14zwq5fe.astroid@yuna.none>
References: <1737975711.7o14zwq5fe.astroid@yuna.none>
MIME-Version: 1.0
X-Ovh-Tracer-Id: 18185535299249641103
X-VR-SPAMSTATE: OK
X-VR-SPAMSCORE: 0
X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeefvddrtddtgdduheegieehucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuqfggjfdpvefjgfevmfevgfenuceurghilhhouhhtmecuhedttdenucenucfjughrpefhvfevufffkffojghfggfgsedtkeertdertddtnecuhfhrohhmpefuihhmohhnucfngffqpfettfffuceoghhithdquddttddurghfgeesshhinhhugidrshhhqeenucggtffrrghtthgvrhhnpefhieeffedufeelgfejueehhffhkeekgfdutdekleduvdehffdtudeijeevhfehjeenucfkphepuddvjedrtddrtddruddpkedvrdeigedrgeehrdduledpfeejrdehledrudegvddrleeinecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehinhgvthepuddvjedrtddrtddruddpmhgrihhlfhhrohhmpehgihhtqddutddtudgrfhegsehsihhnuhigrdhshhdpnhgspghrtghpthhtohepuddprhgtphhtthhopehpvhgvqdguvghvvghlsehlihhsthhsrdhprhhogihmohigrdgtohhmpdfovfetjfhoshhtpehmohehkedvmgdpmhhouggvpehsmhhtphhouhht
X-SPAM-LEVEL: Spam detection results:  0
 AWL 0.000 Adjusted score from AWL reputation of From: address
 BAYES_00                 -1.9 Bayes spam probability is 0 to 1%
 DMARC_MISSING             0.1 Missing DMARC policy
 KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment
 RCVD_IN_DNSWL_NONE     -0.0001 Sender listed at https://www.dnswl.org/,
 no trust RCVD_IN_MSPIKE_H3       0.001 Good reputation (+3)
 RCVD_IN_MSPIKE_WL       0.001 Mailspike good senders
 RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to
 Validity was blocked. See
 https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
 information.
 RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to
 Validity was blocked. See
 https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
 information.
 RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to
 Validity was blocked. See
 https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
 information.
 SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
 SPF_PASS               -0.001 SPF: sender matches SPF record
X-Mailman-Approved-At: Mon, 24 Mar 2025 11:06:34 +0100
Subject: [pve-devel] [PATCH container v2 0/1] close #1543: allow low-level
 lxc config
X-BeenThere: pve-devel@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe>
Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Cc: pve-devel@lists.proxmox.com, git-1001af4@sinux.sh
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: pve-devel-bounces@lists.proxmox.com
Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com>

Hello Fabian,

I added the validify check for each key.

I'm not keen to allow only root@pam to change this setting, as it would 
kill any attempt at automating the container creation via the API.
But maybe it should be part of a permission?



Simon LEONARD (1):
  close #1543: allow low-level lxc config update

 src/PVE/API2/LXC/Config.pm | 17 ++++++++++++++++-
 1 file changed, 16 insertions(+), 1 deletion(-)

-- 
2.48.1


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