From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pmg-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 CD5F01FF13E
	for <inbox@lore.proxmox.com>; Fri, 06 Feb 2026 12:02:01 +0100 (CET)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
	by firstgate.proxmox.com (Proxmox) with ESMTP id BB14B25299;
	Fri,  6 Feb 2026 12:02:35 +0100 (CET)
Date: Fri, 6 Feb 2026 12:02:30 +0100
From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: Samuel FORESTIER <samuel+dev@forestier.app>
Subject: Re: [pmg-devel] [PATCH pmg-api 0/1] user config: password: allows
 (gost-)yescrypt, hashes
Message-ID: <20260206120230.050830ea@rosa.proxmox.com>
In-Reply-To: <20260206115328.74115c4a@rosa.proxmox.com>
References: <576e113b-a610-47d6-99fa-c980e8c96e57@forestier.app>
	<20260206115328.74115c4a@rosa.proxmox.com>
X-Mailer: Claws Mail 4.3.1 (GTK 3.24.49; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2
X-Bm-Transport-Timestamp: 1770375671921
X-SPAM-LEVEL: Spam detection results:  0
	AWL                     0.069 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_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
Message-ID-Hash: UCHU4O5NOJQP3M7EMYIWMRIHG5YCZSF3
X-Message-ID-Hash: UCHU4O5NOJQP3M7EMYIWMRIHG5YCZSF3
X-MailFrom: s.ivanov@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
CC: pmg-devel@lists.proxmox.com
X-Mailman-Version: 3.3.10
Precedence: list
List-Id:  Proxmox Mail Gateway development discussion
 <pmg-devel.lists.proxmox.com>
List-Help: <mailto:pmg-devel-request@lists.proxmox.com?subject=help>
List-Owner: <mailto:pmg-devel-owner@lists.proxmox.com>
List-Post: <mailto:pmg-devel@lists.proxmox.com>
List-Subscribe: <mailto:pmg-devel-join@lists.proxmox.com>
List-Unsubscribe: <mailto:pmg-devel-leave@lists.proxmox.com>

On Fri, 6 Feb 2026 11:53:28 +0100
Stoiko Ivanov <s.ivanov@proxmox.com> wrote:

> Hi,
>..snip..
> It is possible to create a user in the PAM realm (just like in our other
> products) - then you can simply login with the user - and their password
> should be checked by PAM. This has the advantage that you do not duplicate
> the password information and it stays consistent.
Seems I was mistaken on that - currently we do have a few checks which
only allow root in the pam realm - but that could be changed to be more in
line with the other products - if the use-case of having many system-users
accessing PMG is there.