From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id D222A1382C5 for ; Mon, 4 Jan 2021 18:07:27 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6522EE09E0; Mon, 4 Jan 2021 18:07:25 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id BA46FE09C0 for ; Mon, 4 Jan 2021 18:07:24 +0000 (UTC) Subject: Re: [gentoo-dev] Re: [PATCH] acct-user.eclass: don't modify existing user by default To: gentoo-dev@lists.gentoo.org References: <20210104013558.20072-1-whissi@gentoo.org> From: Michael Orlitzky Message-ID: <89a1c171-de56-4f9e-af2a-9140d2be3552@gentoo.org> Date: Mon, 4 Jan 2021 13:07:20 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Archives-Salt: 5b72a443-f46a-46f3-adee-38cdb5939e73 X-Archives-Hash: adc2a15fe6eaf43bc08e2f56da844055 On 1/4/21 11:45 AM, James Cloos wrote: >>>>>> "RHJ" == Robin H Johnson writes: > > RHJ> The best I can come up with at the moment, is that any packaging should > RHJ> detect if there are user modifications, and provide control to users > RHJ> based on that fact. > > Exactly. Akin to etc-update. > We could implement this with something like an /etc/users.d directory that would be populated with entries by either the admin or package manager with CONFIG_PROTECT enabled. Then the system database would be updated by running something like "users-update" (cf. env-update). The essential problem that we need to work around is that e.g. /etc/passwd is "owned" by multiple system packages. I think this would accomplish what you and Robin are talking about, but it wouldn't solve whissi's problem since it's still a Gentoo-specific solution.