From nobody Wed Apr 19 20:51:13 2023 X-Original-To: freebsd-ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Q1tHY129Cz46RN6 for ; Wed, 19 Apr 2023 20:51:21 +0000 (UTC) (envelope-from yuri@aetern.org) Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q1tHX3PY0z40Jj for ; Wed, 19 Apr 2023 20:51:20 +0000 (UTC) (envelope-from yuri@aetern.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=aetern.org header.s=fm2 header.b=xJiD2Qob; dkim=pass header.d=messagingengine.com header.s=fm3 header.b="L pv/9GM"; spf=pass (mx1.freebsd.org: domain of yuri@aetern.org designates 64.147.123.19 as permitted sender) smtp.mailfrom=yuri@aetern.org Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 43D3232004ED for ; Wed, 19 Apr 2023 16:51:18 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Wed, 19 Apr 2023 16:51:18 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aetern.org; h=cc :content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm2; t= 1681937477; x=1682023877; bh=x3RcJja6rWD1gpbgXj7VCE37MGE2ddl0i6M d8UxkXAE=; b=xJiD2QobBP5OtBFd5pxNx0AlufMbhaXr+25VNNWBnADeGwMlLUn t3QgmnuEPiS2MPWHXKt5vpPP2HQfsA/WTu/AAz/pEwO1p2vpaPjU/tt3BvmTqB3d Fuy7STLH3wf8LIXgCBOTQMRxQettjNptLn85lNF0BOgxjgZlZiGnSgosPyD+/BVp uF78vdKSaXA4FHqKwSbrhO7CMZ3z55fEXb3aOUuaD0MejbQqum6SCFcFsoomFNrc 26CYqfV7Ok5yqw6CHiSE+zKuLq9eUcsjSf1Fk/K2j2C4Hb0lOfLEGUL7crOEchSV iQ5XgSZMBKqn7SFj3D/qx1U6Worv3G9a4MA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1681937477; x= 1682023877; bh=x3RcJja6rWD1gpbgXj7VCE37MGE2ddl0i6Md8UxkXAE=; b=L pv/9GMXACU1vFpolpHccT6qKtlq/9GhOxxj2BZgIW3VyOP/jSJb9BCIg2MIwDKQT ae59NdeZtdQyG8eNkKN4isUNvRFB3+A4LGMAnsDNP3o5t7kV+ey+JUieY9Vy8b/K UscC2/F19HaGTjifSlG+6mSYXfY9u+L4zMEfuR0RYMV0G7cpmEyQembMj0nevSKT 8XE6kkUakfZDkeIhTSO9P5pDWkZKgyKs7FOyV9BK/eF9+xz4Kt0sp1S6xc7TJtem ivSL7KjE1ZqD48w3Zb8qfQ1ZUZnhVP4v8RmnjuaroQDENc5T/krMaJNRyfXFtNTR qYoLUyYv/224OOg+eCVZQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfedttddgudehiecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepkfffgggfuffvfhfhjggtgfesth ejredttdefjeenucfhrhhomhepjghurhhiuceohihurhhisegrvghtvghrnhdrohhrgheq necuggftrfgrthhtvghrnhephfetleetleffvefggeegtdehleethfevleekjeffleevhf dvleekteeukeetgefgnecuffhomhgrihhnpeiivghfohigrdgtohhmnecuvehluhhsthgv rhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhephihurhhisegrvghtvghrnh drohhrgh X-ME-Proxy: Feedback-ID: i0d79475b:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Wed, 19 Apr 2023 16:51:17 -0400 (EDT) Message-ID: <648cb930-7708-5032-74a8-471ae4353a6e@aetern.org> Date: Wed, 19 Apr 2023 22:51:13 +0200 List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Subject: Re: Installing mail/mutt erased a user account To: freebsd-ports@freebsd.org References: Content-Language: en-US From: Yuri In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Q1tHX3PY0z40Jj X-Spamd-Bar: / X-Spamd-Result: default: False [-0.40 / 15.00]; R_DKIM_ALLOW(-0.20)[aetern.org:s=fm2,messagingengine.com:s=fm3]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.19]; PREVIOUSLY_DELIVERED(0.00)[freebsd-ports@freebsd.org]; local_wl_from(0.00)[yuri@aetern.org]; DKIM_TRACE(0.00)[aetern.org:+,messagingengine.com:+]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US] X-Rspamd-Pre-Result: action=no action; module=multimap; Matched map: local_wl_from X-ThisMailContainsUnwantedMimeParts: N bob prohaska wrote: > It appears that installing mail/mutt erased a user account. Mutt > was compiled locally using poudriere and installed via pkg from the > local repository. After installation it was still possible to log > in as the regular user, but su asked "Who are you?" when invoked. Don't really see how that is possible, mutt doesn't seem to require/add any user accounts. > It developed that the original username was absent from /etc/passwd > and /etc/master.passwd, but the original home directory was present, > in this case /usr/home rather than /home. > > Re-running adduser as root allowed reinstatement of user login and > su now behaves normally. Adduser didn't report the account as existing, > so how login by ssh worked is mysterious and could be indication of > a recollection error on my part. It could still be present in /etc/pwd.db. > This was on a Pi2 v1.1 running > FreeBSD www.zefox.com 14.0-CURRENT FreeBSD 14.0-CURRENT #22 main-1d35493e46: Tue Apr 18 06:23:00 PDT 2023 bob@www.zefox.com:/usr/obj/usr/src/arm.armv7/sys/GENERIC arm > > In the meantime sendmail was reinstated as the MTA. That's been done > before with no ill effects, but it was a near-simultaneous change that > might have contributed to the confusion. > > I'll chalk this up to faulty wetware unless advised otherwise. My guess would be you somehow reverted passwd files to some default/backup, but didn't run pwd_mkdb? I just tried that adding test user using `pw useradd`, setting password for it, and then removed the line from both passwd files -- I was still able to login via ssh.