From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 254CE1FF141 for ; Tue, 19 May 2026 20:32:40 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id A7F2FFC16; Tue, 19 May 2026 20:32:36 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Dominik Csapak Subject: applied: [PATCH widget-toolkit] location edit: disallow ',' and '=' for the name Date: Tue, 19 May 2026 20:32:22 +0200 Message-ID: <177921554313.2410532.1264311608187638510.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260519133727.3064789-1-d.csapak@proxmox.com> References: <20260519133727.3064789-1-d.csapak@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1779215538582 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.004 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 SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: 2JFOSZJBCB6O5JQ2EVKDYIFAB2LLUZQH X-Message-ID-Hash: 2JFOSZJBCB6O5JQ2EVKDYIFAB2LLUZQH X-MailFrom: t.lamprecht@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Tue, 19 May 2026 15:37:23 +0200, Dominik Csapak wrote: > otherwise one could 'inject' a latitude and longitude into the > value there. The backend still properly checks the property string > anyway. Applied, thanks! [1/1] location edit: disallow ',' and '=' for the name commit: 345cb86eb8fbb1ce187395059f840d15e1aa7420