From nobody Sat May 27 02:12:54 2023 X-Original-To: freebsd-current@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 4QSlgf5ZJ9z4V5MB for ; Sat, 27 May 2023 02:13:02 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (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 4QSlgc21DQz41JP for ; Sat, 27 May 2023 02:13:00 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of junchoon@dec.sakura.ne.jp has no SPF policy when checking 153.125.133.21) smtp.mailfrom=junchoon@dec.sakura.ne.jp; dmarc=none Received: from kalamity.joker.local (123-1-88-210.area1b.commufa.jp [123.1.88.210]) (authenticated bits=0) by www121.sakura.ne.jp (8.16.1/8.16.1/[SAKURA-WEB]/20201212) with ESMTPA id 34R2CsGK025280 for ; Sat, 27 May 2023 11:12:55 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Sat, 27 May 2023 11:12:54 +0900 From: Tomoaki AOKI To: freebsd-current@freebsd.org Subject: Re: Surprise null root password Message-Id: <20230527111254.e9007105f4c5ca6ad8455e72@dec.sakura.ne.jp> In-Reply-To: References: <945C9B6D-F2A8-4F0D-BDB0-49A3DE870168@karels.net> <61e30711-f0da-2f42-3a6f-9bd91fc6b1ce@aetern.org> Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.2) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [0.55 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.996]; NEURAL_SPAM_MEDIUM(0.99)[0.988]; NEURAL_HAM_LONG(-0.84)[-0.843]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; R_SPF_NA(0.00)[no SPF record]; RCVD_TLS_LAST(0.00)[]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[sakura.ne.jp]; HAS_ORG_HEADER(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4QSlgc21DQz41JP X-Spamd-Bar: / X-ThisMailContainsUnwantedMimeParts: N On Fri, 26 May 2023 16:26:06 -0700 bob prohaska wrote: > On Fri, May 26, 2023 at 10:55:49PM +0200, Yuri wrote: > > > > The question is how you update the configuration files, > > mergemaster/etcupdate/something else? > > > > Via etcupdate after installworld. In the event the system > requests manual intervention I accept "theirs all". It seems > odd if that can null a root password. > > Still, it does seem an outside possibility. I could see it adding > system users, but messing with root's existing password seems a > bit unexpected. > > Thanks very much for raising the point! > > bob prohaska Maybe that's it. As you chose "theirs all" (maybe theirs-full?), conflicted files (include /etc/master.passwd) are overwritten by brand-new default ones. You should choose "(e) edit" and manually merge them correctly. -- Tomoaki AOKI