From nobody Fri May 26 20:55:49 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 4QScdk0KNBz4TFkb for ; Fri, 26 May 2023 20:55:54 +0000 (UTC) (envelope-from yuri@aetern.org) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (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 4QScdj3t7Cz3Hcj for ; Fri, 26 May 2023 20:55:53 +0000 (UTC) (envelope-from yuri@aetern.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=aetern.org header.s=fm1 header.b=R67CVWvp; dkim=pass header.d=messagingengine.com header.s=fm1 header.b="X JRNKvg"; spf=pass (mx1.freebsd.org: domain of yuri@aetern.org designates 66.111.4.26 as permitted sender) smtp.mailfrom=yuri@aetern.org Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 923055C00F1 for ; Fri, 26 May 2023 16:55:52 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Fri, 26 May 2023 16:55:52 -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=fm1; t= 1685134552; x=1685220952; bh=nxrGTOpGqz2pgNl+174zSmUeFAr9ChUw2Dj gPxw2ic4=; b=R67CVWvpyUFGBZyYH4k22imzwrnmU3lm8wxOG7/mTDNLRiEzxb9 0ki0Y5zQOPYobePq1jsErpjkFfrYGtrsJWvHLBHxh9wcqptVwbSdSa5FFaDPsukB 9zM8+fjS8XYNmKrBLVgynPrdYbSb4lwD44NFYBQFrGYLKZe9mKgeZx9cSmdNeD5x wWBybqpA9Yi8pH6Zf6NEarEXEGmF++Pva3JpQsmheZhMi8kHGFCZcubgnimXW+Iv AvlZRIw8jH7YXsqp33D4KuT21pTAczGFJ+7CSG0l4oiR8KxLGLWG0QPCaH86WGjD 8FKm+ldnACsV0y1G9fgS4TcWiocllhrbT7w== 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=fm1; t=1685134552; x= 1685220952; bh=nxrGTOpGqz2pgNl+174zSmUeFAr9ChUw2DjgPxw2ic4=; b=X JRNKvgfm95VPQN6nzCMC0BJAN/Pv7QX90Rimfq8RNpiYdPlHXzZCGWLOXbNFfjYI LPNO4l2HBpiClZ2OqeQm9OiJg+A2YOzeVdkXSbzp8fGX3ktLM5nFiGLngn3/z0a6 133KUeds7fPxD+JJ+kI6Nbz3bPPyxemAy73dDLjpu8TJGR1GvbiZlKKgx99mkwjD uzV169R3kQAMUur3s6RvCQezU47vMHbgqPrORhTWzGrXmq1L7bSoXXaxDu1PadEe TWjrO8jpG9cn2Cz0mTotusn5rfh1S/3cqE9RHVeqpXFzbpcIIoOCJ/pwIsyztsjV ABfnzkeBjknHCEoG7/GBQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeejledgudehfecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepkfffgggfuffvfhfhjggtgfesth ejredttdefjeenucfhrhhomhepjghurhhiuceohihurhhisegrvghtvghrnhdrohhrgheq necuggftrfgrthhtvghrnhepffetheejjeehleegkedvueekueeghfdtvdefffeluedvhe ekteejkefgveegfedvnecuffhomhgrihhnpeiivghfohigrdhorhhgnecuvehluhhsthgv rhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhephihurhhisegrvghtvghrnh drohhrgh X-ME-Proxy: Feedback-ID: i0d79475b:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Fri, 26 May 2023 16:55:51 -0400 (EDT) Message-ID: <61e30711-f0da-2f42-3a6f-9bd91fc6b1ce@aetern.org> Date: Fri, 26 May 2023 22:55:49 +0200 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 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: Surprise null root password Content-Language: en-US To: freebsd-current@freebsd.org References: <945C9B6D-F2A8-4F0D-BDB0-49A3DE870168@karels.net> From: Yuri In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4QScdj3t7Cz3Hcj X-Spamd-Bar: / X-Spamd-Result: default: False [-0.40 / 15.00]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.26]; R_DKIM_ALLOW(-0.20)[aetern.org:s=fm1,messagingengine.com:s=fm1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; local_wl_from(0.00)[yuri@aetern.org]; DKIM_TRACE(0.00)[aetern.org:+,messagingengine.com:+]; ASN(0.00)[asn:19151, ipnet:66.111.4.0/24, country:US] X-Rspamd-Pre-Result: action=no action; module=multimap; Matched map: local_wl_from X-ThisMailContainsUnwantedMimeParts: N bob prohaska wrote: > On Fri, May 26, 2023 at 07:48:04PM +0100, Ben Laurie wrote: >> -T on ls will give you full time resolution... >> > More's the wonder: > root@www:/usr/src # ls -lT /etc/*p*wd* > -rw------- 1 root wheel 2099 May 10 17:20:33 2023 /etc/master.passwd > -rw-r--r-- 1 root wheel 1831 May 10 17:20:33 2023 /etc/passwd > -rw-r--r-- 1 root wheel 40960 May 10 17:20:33 2023 /etc/pwd.db > -rw------- 1 root wheel 40960 May 10 17:20:33 2023 /etc/spwd.db > > For sake of clarity, /etc/master.passwd's root line is > root::0:0::0:0:Charlie &:/root:/bin/sh > while /etc/passwd's root line is > root:*:0:0:Charlie &:/root:/bin/sh > > I just noticed a second host (Pi3) which is similarly affected. > It completed a build/install cycle on May 25, uname -a yields > FreeBSD www.zefox.org 14.0-CURRENT FreeBSD 14.0-CURRENT #46 main-n263122-57a3a161a92f: Thu May 25 21:25:57 PDT 2023 bob@www.zefox.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64 > > On this host I get > root@www:/usr/src # ls -lT /etc/*p*wd* > -rw------- 1 root wheel 1796 Nov 12 16:00:03 2022 /etc/master.passwd > -rw-r--r-- 1 root wheel 2430 Oct 1 19:40:22 2020 /etc/passwd > -rw-r--r-- 1 root wheel 40960 Oct 1 19:40:22 2020 /etc/pwd.db > -rw------- 1 root wheel 40960 Oct 1 19:40:22 2020 /etc/spwd.db > (at least the dates make more sense) > > The root line in /etc/master.passwd is > root::0:0::0:0:Charlie &:/root:/bin/sh > > I didn't catch any null password reports in the security emails, > most likely through lack of attention. As with the first case, > passwords seem to work normally (null rejected, normal accepted). The question is how you update the configuration files, mergemaster/etcupdate/something else?