From owner-freebsd-ports@FreeBSD.ORG Sun Nov 10 19:59:29 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 60445A44 for ; Sun, 10 Nov 2013 19:59:29 +0000 (UTC) (envelope-from ohauer@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EA0D92E2E for ; Sun, 10 Nov 2013 19:59:28 +0000 (UTC) Received: from [192.168.0.100] ([87.139.233.65]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0LbdE3-1W2oEv3H6B-00lAML for ; Sun, 10 Nov 2013 20:59:26 +0100 Message-ID: <527FE5A9.1010002@gmx.de> Date: Sun, 10 Nov 2013 20:59:37 +0100 From: olli hauer User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: FreeBSD Ports Subject: Re: Staging break user account modification in post-install References: In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:EszMXOhz+Jk3oZnZgFq8E+mQxegdzFY0mgIyaQZ26o7i/kHTrSX jYKQMQxdwsMteXzgv+vOmG8k8FoLjGO+XmjDDWWV1z2tgUXyG4QwwMf8N75B7m/DjpIZdLt Vzz8AdyGqTpd/gPMECrIZoXBrlsbHG+Q/asy+pEmqqkKg1XlKJsQHFi4VZVJ16VbRYqYeOd OLVsdMhq2BQlg8vdnwxvA== Cc: Aryeh Friedman X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Nov 2013 19:59:29 -0000 On 2013-11-10 20:40, Aryeh Friedman wrote: > post-install is now called *BEFORE* users are created (before staging was > added it was after)... looking at bsd.port.mk there seems no reasonable > target that replaces post-install for this purpose. Namely I need to lock > the user account that was created and assign a default password to it. > This is what I had that used to work: > > post-install: > echo password|pw usermod user -h 0 2>/dev/null > pw lock user Is the account always locked? If yes what is the difference to create a user without any password and assigning '/usr/sbin/nologin' as shell? What happens to the account without staging if installed from a package? Without pkg-install script the account keeps unmodified or even is not created ... In case you use a pkg-install script, then it will be executed only during installation and stage is one step before. -- olli