From nobody Sun May 21 01:37:30 2023 X-Original-To: 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 4QP39Z2PRYz4Bp8R for ; Sun, 21 May 2023 01:37:38 +0000 (UTC) (envelope-from grog@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QP39Z1zNvz4WtB; Sun, 21 May 2023 01:37:38 +0000 (UTC) (envelope-from grog@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1684633058; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=66hPFUjhb4bBv4bclx7ygkkl2muj62wjP9mOVxL9ONQ=; b=S81/4pDmDwwyg1/vLv9j93sY3hc1YbzBRbrh+3l6uMODwdkKZh0PBWTB+Zc8RBkovTfgby M9VQX++0i7VmdVo8TO3BmOQeCSkBCXw0MFSHs7Tkc9VRFfe/6IcuLVjR5FVQBQ0qBfffnU bx5DQ5EkRV5sBFBlGh2PpUSL4KIDc2zijd9FsOuedtTYalPXEQb2JmVL7VsbWPX44cBA6e L5hhbWt07r0GeYG5euUKsj1Y1wy1tkz10GTiBM9YK8OdJ0jBy9ZlLGj+W4cRlJ43TkuPw+ R4a9IA1K80IGScBBp3YdqWX9uZWA0sNV4Fvf92ECkzqEz0XbPGDSERksWK1U5Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1684633058; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=66hPFUjhb4bBv4bclx7ygkkl2muj62wjP9mOVxL9ONQ=; b=VxKvT/pU2FhygFUrXHvinjMga2i2iZtUZQtZasg11Vm7VYnXMvMVr9n4CA7gRVpPDD2i0b NGWTNpja6c3rFpBxSSe1Pmc87IQur8Y6B1/jWyMVS5gFh4PElfHuLrEc4iDHIDh7Gg5ysG r7QR+xoPQ33SiO24WQVG6J/f0gT0SxUbQfU9vq32GasRDSHmc2dyF4HtlqX8uh/AGVipp0 B7Vq+WH41odDgldxu9Qd72lBSVoytMpICszVHGChV+OgRlXdVk87hgrfp7oD1ugQ8oBNKy TgkXx7F6QvUIlYqXFfHrfcY2s3qxFVfdnlGvW8f8IfHb/9uKhz3Ap6Vaydb30Q== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1684633058; a=rsa-sha256; cv=none; b=SYgX70ToMjCENiqhuZqboro+naW8AEal7h/2Ui2XPXGq4XLHxUZW/cibseoFTbXNqh18/C 0Ti2EPd347FD/0cNP+JCadlDEV9evzL47+D5m9cPcLezYHZ9wICGEG8RurG7r2htnV7bCM ktYc390zUdve7Tl3EpM1JisDgNM5k5borvRb+YPNVXlNclUgOPxwFHnHEZP27YP32nrT9C /8C0dLL5OECv4fi3imkz6h4GDkYco28uNBRMkQJJ/TbH+CLZHnLs9U6QnremFPWQWZU+Hm qxwgTZhP9RaNLLFup0ZX++8NeIHYSidBR4tNvNdVcsQpujQJWDgUrHjHdUhQGg== Received: from eureka.lemis.com (121-200-11-253.79c80b.mel.nbn.aussiebb.net [121.200.11.253]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: grog/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4QP39X63w3zMHD; Sun, 21 May 2023 01:37:36 +0000 (UTC) (envelope-from grog@FreeBSD.org) Date: Sun, 21 May 2023 11:37:30 +1000 From: Greg 'groggy' Lehey To: Mike Jakubik Cc: Yuri , current@freebsd.org Subject: Re: FreeBSD wont boot on AMD Ryzen 9 7950X Message-ID: <20230521013730.GC51020@eureka.lemis.com> References: <22BF4CF1-FA3A-4901-B365-A7F1353BE50F@joscomputing.space> <5fa6ffa2-2cfa-d5e6-7891-7e9388a81f3e@aetern.org> 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: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="H8ygTp4AXg6deix2" Content-Disposition: inline In-Reply-To: Organization: The FreeBSD Project Phone: +61-3-5309-0418 Mobile: +61-490-494-038. Use only as instructed. WWW-Home-Page: https://www.FreeBSD X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 User-Agent: Mutt/1.6.1 (2016-04-27) X-ThisMailContainsUnwantedMimeParts: N --H8ygTp4AXg6deix2 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Saturday, 20 May 2023 at 17:15:25 -0400, Mike Jakubik wrote: > On Sat, May 20, 2023 at 4:49=E2=80=AFPM Yuri wrote: >> Mike Jakubik wrote: >>> >>> Thanks for the info. At least I know it's not specific to my parts. Is >>> there any knob one can turn in the BIOS to enable/disable this feature? >>> iirc UART is old school serial ports? Wonder if removing UART support >>> from the kernel would be a workaround. >> >> Try the following from the loader prompt (option 3 from the beastie menu= ): >> >> set hint.uart.0.disabled=3D1 >> set hint.uart.1.disabled=3D1 >> boot > > That did the job! Good to hear. But it's a workaround, of course. I hope you have entered a PR so that somebody can fix the problem. Greg -- Sent from my desktop computer. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft mail program reports problems, please read http://lemis.com/broken-MUA.php --H8ygTp4AXg6deix2 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAmRpddoACgkQIubykFB6QiOongCfWUM3u5Ge/zeHKm0+5+sdWh1Z lzAAoKx6Ba5uerOgTjVPNn2sljJELr+I =elxX -----END PGP SIGNATURE----- --H8ygTp4AXg6deix2-- From nobody Sun May 21 13:49:33 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 4QPMQ23YGyz4CWsn for ; Sun, 21 May 2023 13:49:30 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QPMQ02jRKz4N46 for ; Sun, 21 May 2023 13:49:28 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net; dmarc=none Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.17.1/8.15.2) with ESMTPS id 34LDnYiu003959 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sun, 21 May 2023 06:49:34 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.17.1/8.15.2/Submit) id 34LDnYR7003958; Sun, 21 May 2023 06:49:34 -0700 (PDT) (envelope-from fbsd) Date: Sun, 21 May 2023 06:49:33 -0700 From: bob prohaska To: freebsd-current@freebsd.org Cc: bob prohaska Subject: Stray characters in command history Message-ID: 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-Disposition: inline X-Spamd-Result: default: False [-1.02 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_SHORT(-0.99)[-0.990]; NEURAL_HAM_MEDIUM(-0.99)[-0.987]; NEURAL_HAM_LONG(-0.94)[-0.940]; MID_RHS_WWW(0.50)[]; WWW_DOT_DOMAIN(0.50)[]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; R_DKIM_NA(0.00)[]; R_SPF_NA(0.00)[no SPF record]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_COUNT_THREE(0.00)[3]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[zefox.net]; TO_DN_SOME(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4QPMQ02jRKz4N46 X-Spamd-Bar: - X-ThisMailContainsUnwantedMimeParts: N Lately I've been playing with buildworld on a Pi3 running -current. The same machine acts as a terminal server for a second Pi3 also running -current in my "cluster". I ssh into the first Pi3, su to root and run tip to pick up a serial connection to the second Pi's console. Both machines are within a week of up-to-date. While building world on the first Pi3 the ssh connection frequently drops and must be re-established. If there was a shell running on the serial console of the second Pi3 it typically keeps running and when the tip session is restarted disgorges a stream of accumulated console message. This morning the same thing happened, but I noticed something odd. The stream of messages (all login failure announcements from ssh) ended with .... May 21 06:15:00 www sshd[33562]: error: Fssh_kex_exchange_identification: banner line contains invalid characters *+May 21 06:15:19 www sshd[33565]: error: Fssh_kex_exchange_identification: Connection closed by remote host May 21 06:15:33 www sshd[33613]: error: Protocol major versions differ: 2 vs. 1 At that point I hit carriage return and got *+: No match. I did not type the *+ so it looks like the characters were somehow introduced elsewhere, possibly from the ssh failure message. How they got into the command stream is unclear. This strikes me as undesirable at best and possibly much worse. The shell reporting the "no match" was a regular user shell, but if I'd been su'd to root it appears that the unmatched characters would be seen by the root shell as input. This more-or-less fits with the pattern seen earlier with reboots observed via serial console halting on un-typed keystrokes. Those halts were attributed to electrical noise on the serial line, but this looks like something injected via part of the network login process. Reboot pauses have been an ongoing phenomenon for months, this is the first time I've noticed the "invalid characters" message from ssh on the console. Thanks for reading, apologies if I'm being a worrywart. bob prohaska From nobody Sun May 21 18:40:47 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 4QPTsx22dwz4CKf2 for ; Sun, 21 May 2023 18:40:37 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QPTsw4mlDz3s7p for ; Sun, 21 May 2023 18:40:36 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Authentication-Results: mx1.freebsd.org; none Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.17.1/8.15.2) with ESMTPS id 34LIel9J004674 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sun, 21 May 2023 11:40:47 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.17.1/8.15.2/Submit) id 34LIelog004673; Sun, 21 May 2023 11:40:47 -0700 (PDT) (envelope-from fbsd) Date: Sun, 21 May 2023 11:40:47 -0700 From: bob prohaska To: freebsd-current@freebsd.org Cc: bob prohaska Subject: Re: Stray characters in command history Message-ID: References: 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-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4QPTsw4mlDz3s7p X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Here is another example, perhaps a bit clearer. The ssh connection to the first Pi3 in the chain had dropped, so it was re-establishing via a regular user login, then su was invoked and tip run: ..... To change this login announcement, see motd(5). Want to go the directory you were just in? Type "cd -" bob@pelorus:~ % su Password: # tip ucom Stale lock on cuaU0 PID=2487... overriding. connected osed by r31 www s <<<< This appeared spontaneously, then I hit return. osed: Command not found. <<<<< I didn't type anything. bob@www:/usr/src % <<<<< The shell prompt on the 2nd Pi3's serial console. .... Clearly nothing to do with sshd, might it simply be a misdirected echo of console output generated by a (dead or broken) tip connection? The first example looked possibly malicious, this does not.... Thanks for reading, bob prohaska On Sun, May 21, 2023 at 06:49:33AM -0700, bob prohaska wrote: > Lately I've been playing with buildworld on a Pi3 running -current. The same machine > acts as a terminal server for a second Pi3 also running -current in my "cluster". > I ssh into the first Pi3, su to root and run tip to pick up a serial connection to > the second Pi's console. Both machines are within a week of up-to-date. > > While building world on the first Pi3 the ssh connection frequently drops and must be > re-established. If there was a shell running on the serial console of the second > Pi3 it typically keeps running and when the tip session is restarted disgorges a > stream of accumulated console message. > > This morning the same thing happened, but I noticed something odd. The stream of > messages (all login failure announcements from ssh) ended with > > .... > May 21 06:15:00 www sshd[33562]: error: Fssh_kex_exchange_identification: banner line contains invalid characters > *+May 21 06:15:19 www sshd[33565]: error: Fssh_kex_exchange_identification: Connection closed by remote host > May 21 06:15:33 www sshd[33613]: error: Protocol major versions differ: 2 vs. 1 > > At that point I hit carriage return and got > *+: No match. > > I did not type the *+ so it looks like the characters were somehow introduced elsewhere, > possibly from the ssh failure message. How they got into the command stream is unclear. > > This strikes me as undesirable at best and possibly much worse. The shell reporting > the "no match" was a regular user shell, but if I'd been su'd to root it appears that > the unmatched characters would be seen by the root shell as input. > > This more-or-less fits with the pattern seen earlier with reboots observed via serial > console halting on un-typed keystrokes. Those halts were attributed to electrical noise > on the serial line, but this looks like something injected via part of the network > login process. Reboot pauses have been an ongoing phenomenon for months, this is the > first time I've noticed the "invalid characters" message from ssh on the console. > > Thanks for reading, apologies if I'm being a worrywart. > > bob prohaska > > > From nobody Mon May 22 15:00:00 2023 X-Original-To: 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 4QQ0xH1Jpgz4BYZq for ; Mon, 22 May 2023 15:00:19 +0000 (UTC) (envelope-from garyj@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mout.gmx.net", Issuer "Telekom Security ServerID OV Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QQ0xG0Hv0z3H2B for ; Mon, 22 May 2023 15:00:17 +0000 (UTC) (envelope-from garyj@gmx.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmx.de header.s=s31663417 header.b=JbQjnVfQ; spf=pass (mx1.freebsd.org: domain of garyj@gmx.de designates 212.227.17.20 as permitted sender) smtp.mailfrom=garyj@gmx.de; dmarc=pass (policy=none) header.from=gmx.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.de; s=s31663417; t=1684767615; i=garyj@gmx.de; bh=cbgaLHBTJdo5kXqjuSLf5V+B18ntSoVOGrZVAJghe8I=; h=X-UI-Sender-Class:Date:From:To:Subject:Reply-To; b=JbQjnVfQORIs9z1LMLt+zq2Gm8tmHputbVBPeZsXyYGBQ9Zv5FQQ4i3rYX9jQ6u/J aMcZN4QgPqhuSEUks35p/pR6IVifQzmUx2jIq6UXWQHTRza0E/TJZPGzMF/1t5zeSR kmUt3PI22FWPm/g01yNZcL4eysUS5A8mEoFRvP3rXyeZVE2TMNpgiq8zgnGOKbv7uc uOG/WSJ5JWX7NB1myfvRfFXCtAAPT5/WTf39CG8BS/KspJD8Ub1fPQ3KuWtEGHWzfo aMKAtGCQtl9ICa9vGj5oCzplneAza/VrbpfhB1KnpoyP5rgmsshEFx8krx70dQCLme xFLcP9WQ/mtTQ== X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a Received: from ernst.home ([91.59.238.143]) by mail.gmx.net (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MOiDX-1pm5EO2kRj-00QFpe for ; Mon, 22 May 2023 17:00:15 +0200 Date: Mon, 22 May 2023 15:00:00 +0000 From: Gary Jennejohn To: current@freebsd.org Subject: builworld fails due to error in af_inet.c Message-ID: <20230522170000.25468c5f@ernst.home> Reply-To: garyj@gmx.de X-Mailer: Claws Mail 3.19.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) 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: quoted-printable X-Provags-ID: V03:K1:cfZ3hUi5YE6zX1wie7B/1Xn1LTnBSJz979Kk1tdtzoBk61qDIc4 RG93ZeJdSQKyHreE7fkgMOpncFnxkUbC+B0brhtG8x16++GfIt40D8y7kIBGLwH4dqSX9fo UNYN8XC69milg2r1MfNMicfqT9j3Z3j9pKJpsWK3YeaU6Sg9dsXYqzCO07zlv2Sri4bFY2E AqEfjiScXiwocbJeNBp+Q== X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:WuAtsqk2GHE=;E1KNb3QquQogMyiqOo+JbZNCSsm WLLXj8Kxlmh/79Y+GquD4lpXwbPWJYMo73AjutD/zptAIxalDCCsU+H1XKsHcvDJzTtJeEvxu 7zYEBBTf0612CJCitgxQ/ggU1OwWfUaKDDn2V0nNXEv17+JOveQwlA4KlVJ0oYutBuNsVc3ee YiO8v9SI5yzFx0wnh7ipDj9s264ttwLxyhdX5KwYKr0OmG/toYgL6+5UH4N6ZlPK3Ze6dVckO g5tMrzp9J8/RGZk7Msql6APRHeI+eRXS8zD72/lycrB6WZ1QFryI/e2SGKx7w1eB5WUS7qqPS xuiqZocflc++WJELQW4rj+G5ZxlFmos0zM5betrvGIiRc/WNGpEc9m5PdloQDTpRN2V41IGK8 2RnymQSG1KWdK2cvffsH7qbKG0URgXrVzeLWoj9Ii483Ypkt8XgQvA9da6kF+D0roxESdQ7kt 6ZgkgxNvKpUfCCVcNeTIhiGzv2hfgnEHZ6ELhxQHWjfdHKz8pnOGJzHcAJ2Xb5ChLpyTbJeWf OvnYXUYKfR+dggRexPiu83/sEQGre0JuE0mfwrQaK/p3ctuF8amOuZaT4TWN1OaHnr3JMqJFq ktdR+LvNK23Z1ErahPmrd+tH/4IQ4PgrPi0dUXWVgD1A0+/kaVM8u6rbv5CsiGGDSyz4UyGsV qDbxnxJ+0pMiPcEP2jwnBnQaA4Q4xU73g7Lajd+Wiwn6QsQrEsXoa+dGlanvqcJM7b87iJ3x9 /y5NNA1NonLT/g4mWWNUqa8ZGDeFgcPnlMxyoMZJdy4mxQD8PMSMlIBXA14M1Tgvy9elUkJzt vqVdOrzyHihgBYrwdtNVx/hBRF5HGs7d1Gdzo8yp2Q/S/es23oj2/pnRcQQ3F4BncfnOpE3j8 fXeSx7y0AGYk9X747aiFPuYbtocLZMvN0C4tZRCUOGPKk8NCxPaBT+35hcs6Z7QGnuZDyT3zr EHbl+xakccKFY0hA231/7iR5Kfc= X-Spamd-Result: default: False [-2.09 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_SPAM_MEDIUM(1.00)[0.999]; NEURAL_HAM_SHORT(-0.99)[-0.986]; DMARC_POLICY_ALLOW(-0.50)[gmx.de,none]; R_DKIM_ALLOW(-0.20)[gmx.de:s=s31663417]; R_SPF_ALLOW(-0.20)[+ip4:212.227.17.0/27]; RCVD_IN_DNSWL_LOW(-0.10)[212.227.17.20:from]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; HAS_REPLYTO(0.00)[garyj@gmx.de]; RCPT_COUNT_ONE(0.00)[1]; RWL_MAILSPIKE_POSSIBLE(0.00)[212.227.17.20:from]; FREEMAIL_REPLYTO(0.00)[gmx.de]; MLMMJ_DEST(0.00)[current@freebsd.org]; BLOCKLISTDE_FAIL(0.00)[212.227.17.20:server fail,91.59.238.143:server fail]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE]; REPLYTO_ADDR_EQ_FROM(0.00)[]; FREEMAIL_FROM(0.00)[gmx.de]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[gmx.de:+]; FREEMAIL_ENVFROM(0.00)[gmx.de]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4QQ0xG0Hv0z3H2B X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N I just ran buildworld using the latest current source. It dies due to this error in line 385 of /usr/src/sbin/ifconfig/af_inet.c: static void warn_nomask(ifflags) The compiler really doesn't like not seeing a type for ifflags and bails out as the result. Strangely enough, in_proc() a few lines later clearly has int ifflags in its list of variables. Setting ifflags to int in warn_nomask() fixes the build. Wasn't this compile tested before it was committed? =2D- Gary Jennejohn From nobody Mon May 22 15:02:30 2023 X-Original-To: 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 4QQ1090MY0z4BZ6s for ; Mon, 22 May 2023 15:02:49 +0000 (UTC) (envelope-from garyj@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mout.gmx.net", Issuer "Telekom Security ServerID OV Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QQ10766Dfz3JQD for ; Mon, 22 May 2023 15:02:47 +0000 (UTC) (envelope-from garyj@gmx.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmx.de header.s=s31663417 header.b=kOJJnWxQ; spf=pass (mx1.freebsd.org: domain of garyj@gmx.de designates 212.227.15.18 as permitted sender) smtp.mailfrom=garyj@gmx.de; dmarc=pass (policy=none) header.from=gmx.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.de; s=s31663417; t=1684767765; i=garyj@gmx.de; bh=57KXeZ9Bi80bOzPwDon+HifDY3N5T24p5RIkdy5aNUE=; h=X-UI-Sender-Class:Date:From:To:Subject:In-Reply-To:References: Reply-To; b=kOJJnWxQZ5Ut1GXfFWFQTTIYZmhM+Gl17xSormO4GvPGp4j/yJ0yrsx6Z8VP0gSHF GwM05eAz4wjhEEqDZaC105xCoo/r1AZKjh71vOvS1p1HYPycwws/0+BeKpEeFxD53I MIt+EG+czenYup5fUKim/CXz+qj0qhPgh23W5FaI7LXKq0C/NqUzM0aCLwiIWgD40L r6VYR9UiynB2mbCjko/0XQ8fNMal6VCCsrMYzIE3Cd+q3DaHeYRi1kRuffGlTZnq5K N6z1zRswwutUPQe2FyDP+G303izdROyNnv3KsMiBy89w4YSHe+9iZo0e7GAkF+lMEb zErIYMWWiVyWQ== X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a Received: from ernst.home ([91.59.238.143]) by mail.gmx.net (mrgmx004 [212.227.17.190]) with ESMTPSA (Nemesis) id 1Msq2E-1qGS7R2pXE-00t91M for ; Mon, 22 May 2023 17:02:45 +0200 Date: Mon, 22 May 2023 15:02:30 +0000 From: Gary Jennejohn To: current@freebsd.org Subject: Re: builworld fails due to error in af_inet.c Message-ID: <20230522170230.279d3154@ernst.home> In-Reply-To: <20230522170000.25468c5f@ernst.home> References: <20230522170000.25468c5f@ernst.home> Reply-To: garyj@gmx.de X-Mailer: Claws Mail 3.19.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) 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: quoted-printable X-Provags-ID: V03:K1:WhmcWH5jlahxo9oi5sXF20vl7wqXj0VPdjmbXEUL1ppRzFbANGd hJWARV/ysaRODXkGBaUfv7D45H/ZZPiHCUpwg1DemqH8wgXa9NABZiNlFSOz6OdRRrWWAff W9HHv7skQwnGdma2r0I8dniD4Sr4zXu8frFFcB4Gwvs8axQcmAhpMtwLSiqUVsKmtaQ1ImD eHI8DPfbMerr4e8kChZEQ== X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:n/GWRZCJ+8M=;c1fAd+FDZhzoV8Lr/uyPLAElqbA MClna6csXSk4yrB7cg6it2eq0b5AABFa+8LFemBxcdqKhbJ1wDf39fPPFVmd8/ZKJPF4Jx767 HmCb80HsQVHuMo2+z1izJhEH4S4yBEqx4lj5gYz1hvVtT4uYDHz4zjRifSCc+N8nzugAM1zgn 6ps/5QYSsfj6c6s8foOLZa+7iEkHOu5gD05DvTpMGt9w4lbOTfL7EEbQljc2n9fYRsFEA5vmJ 9+ffefxm6z1/VsAkFX4aswtxHSZ5JXPeX/uSWNQimFfCsONYUupe9eUbAEvJ9vbB47e7zpYfo mZ/Boc7UByvhdf58MiwJGB0dws0Ej9tmVpv6j5bC75PLzO3GBBnNoawFaOp+MXpkbx/c+o8+I qDYXkiG6tK4GbH5rzz+pOyf5n+a3WroUYNnEoGODfLSQ5QiH+OXuZXsR/StW8oMJqiE1zUepv fKFq3TqhsSACh9HXV97SZmfStwHEcQhCCcBPuV/qfok9SJlj0wgyjkO1Vf1cpTtWnuUbb1Lyf tRuk9RTYhac7PlH4Ez4BJh5K6tN14WuHu8uJweASC42fNV30QiRGCXPfHFFiFrVfRoXqDTX2o SUXMNTTW+AITchB9OVzVC3IyVlPDRtK1O1tFV3xeVqVX7t40lHtIQcNdckfzLvkeoh4l8EYSt LU5j2zkZENirm0ehCB3Nm5Atyjv38CUj7fE+GAetmcd7bTmdIj8R8qucE//65fogIu29B6dsY j5AqWeWrQvM3J/V8wpdO3C8n36pIEtN3XNAnuUIk0uTLxdioJU99fGsMcu18XcQMOV8bV7BER d+EZOecPvyBvL4MMa2oYqs9NIoXPae/DUjDleX4/Fqyw0ywwODBHZ/aE0pyoqUhfr0BIeanW/ kslqKnvk3C8ke+haXbEUnwL/lPU0+PyCjA16yVSmx3wD9crpWyFf66wxCgBJsPu2r0kWAriT1 Bxv2p1pp45EfYE2EVQBLWTel9wA= X-Spamd-Result: default: False [-3.06 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.990]; DMARC_POLICY_ALLOW(-0.50)[gmx.de,none]; R_SPF_ALLOW(-0.20)[+ip4:212.227.15.0/25:c]; R_DKIM_ALLOW(-0.20)[gmx.de:s=s31663417]; RCVD_IN_DNSWL_LOW(-0.10)[212.227.15.18:from]; MIME_GOOD(-0.10)[text/plain]; NEURAL_SPAM_MEDIUM(0.03)[0.028]; MLMMJ_DEST(0.00)[current@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[212.227.15.18:from]; RCPT_COUNT_ONE(0.00)[1]; FREEMAIL_REPLYTO(0.00)[gmx.de]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; HAS_REPLYTO(0.00)[garyj@gmx.de]; RCVD_COUNT_TWO(0.00)[2]; REPLYTO_ADDR_EQ_FROM(0.00)[]; TO_DN_NONE(0.00)[]; FREEMAIL_FROM(0.00)[gmx.de]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[gmx.de:+]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE]; FREEMAIL_ENVFROM(0.00)[gmx.de]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4QQ10766Dfz3JQD X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N On Mon, 22 May 2023 15:00:00 +0000 Gary Jennejohn wrote: > I just ran buildworld using the latest current source. > > It dies due to this error in line 385 of /usr/src/sbin/ifconfig/af_inet.= c: > > static void > warn_nomask(ifflags) > > The compiler really doesn't like not seeing a type for ifflags and bails > out as the result. > > Strangely enough, in_proc() a few lines later clearly has int ifflags in > its list of variables. > > Setting ifflags to int in warn_nomask() fixes the build. > > Wasn't this compile tested before it was committed? > Woops! It turns out that my source was NOT fully up to date. I just saw that af_inet.c was fixed. Sorry for the noise. =2D- Gary Jennejohn From nobody Mon May 22 15:03:37 2023 X-Original-To: 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 4QQ11L1vl2z4BYsZ for ; Mon, 22 May 2023 15:03:50 +0000 (UTC) (envelope-from melifaro@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QQ11L1N3gz3Kd4; Mon, 22 May 2023 15:03:50 +0000 (UTC) (envelope-from melifaro@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1684767830; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=tudMQfzVBY+xOtU4l45z181Wv2Tfnm67WR7zXR4ZsL0=; b=mcohT3wOpx3EuptOPclXnCeSF4+d0bx03XVSYD0cREm0pnjRISYebsJxeetAm1qSwERt15 XStXi02SCQDhy824WjAh/fqzu6KbBli47gBmysvOfisepGlx0PMTnc1L9aKbtQZAIXwmcn M4yF/uyesVNC5qCLT1OUZjTajzIUvV2BQRSAqgkrJlLrFaZlhwqxHNtRJYAFN5PYz2QTy4 NmL5UWdSC5a7kzMsDf1eBVbrBK7NQ7Gc+DXWTBPn3OjfT5KRtBqSqOX11k6iyyM8mD3H6w c+3nz8K3OY/XV2VggXWRet1+7rOrBmxbs+93PAYcnO8jjpQ7rh6D8irT99oMCQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1684767830; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=tudMQfzVBY+xOtU4l45z181Wv2Tfnm67WR7zXR4ZsL0=; b=cQMq2ctGJ6us8nlsL2aw8Wyw7eaWDR2reGxhhP2SgxWoxvOw05QG9+/cEtyGxLTJD3eb0B FQsj8oIgk/yvCMBkDBI0YCERWjJmfXwNKFpcrHwyeczy2EjO+suoyazM+aharFqY5I5+Pd qQr7ywGDVb245oQBOFNAVXlTRQ33knh01F57TYmNUO1BWd+45mR5hHJycJJhyqTV8/7QtX IVoGn/nFlLuXQT0TGXZtZMPfpA1lJFvfIhSpcsDpdIxnvi54sqqi9k09GZi5oTcaBseF48 x/DZLply/RaJKHwrYwfYB+lW6UtyViAIcqT2VEG042Q0JrpnF+eTIYblpxtzHQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1684767830; a=rsa-sha256; cv=none; b=kMSbzdonDKAwtrKyB4TQQViXzLT216foOkzPui9OjJJXEAh6NY/uYK8XI0xh+n53v/JKBE kYMf4aWxrcBFlG9wnvX1t6Paw13SZymr1bljTB0mSfBqDj5Bde15o4+JT+HagIkXyIlSkh fF3FvRcQ4LVYf7kZ+ah7IeDiOj2vhEUn+jiA/3D/lVflCu6j2zPkL/adpBUdrdWDU668BN za7XhNEmV1zCpv5t8n05IzDBUZmDyZkckGyuaJrH2//4AVzV3quboNPSlVYd3p0DAJrYZc wM13N7CpizDsUQ1e+abRYwjafP5ZiKgkPMialpzeGOPNTx/w08rjY7HcXftngg== Received: from smtpclient.apple (unknown [IPv6:2a02:8084:d6bb:510:a966:d3d6:9789:8d0a]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: melifaro/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4QQ11K59Vvz15KD; Mon, 22 May 2023 15:03:49 +0000 (UTC) (envelope-from melifaro@FreeBSD.org) Content-Type: text/plain; charset=utf-8 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 (Mac OS X Mail 16.0 \(3731.400.51.1.1\)) Subject: Re: builworld fails due to error in af_inet.c From: Alexander Chernikov In-Reply-To: <20230522170000.25468c5f@ernst.home> Date: Mon, 22 May 2023 16:03:37 +0100 Cc: current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <1B5092E2-27AB-45B7-B726-F83B6986638D@FreeBSD.org> References: <20230522170000.25468c5f@ernst.home> To: garyj@gmx.de X-Mailer: Apple Mail (2.3731.400.51.1.1) X-ThisMailContainsUnwantedMimeParts: N Sorry for the breakage (and thanks for markj@ for the prompt fix) > On 22 May 2023, at 16:00, Gary Jennejohn wrote: >=20 > I just ran buildworld using the latest current source. >=20 > It dies due to this error in line 385 of = /usr/src/sbin/ifconfig/af_inet.c: >=20 > static void > warn_nomask(ifflags) >=20 > The compiler really doesn't like not seeing a type for ifflags and = bails > out as the result. >=20 > Strangely enough, in_proc() a few lines later clearly has int ifflags = in > its list of variables. >=20 > Setting ifflags to int in warn_nomask() fixes the build. >=20 > Wasn't this compile tested before it was committed? It was & it didn=E2=80=99t yell on my setup. >=20 > -- > Gary Jennejohn >=20 From nobody Mon May 22 15:37:53 2023 X-Original-To: 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 4QQ1n00wjmz4Bc5t for ; Mon, 22 May 2023 15:38:12 +0000 (UTC) (envelope-from garyj@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mout.gmx.net", Issuer "Telekom Security ServerID OV Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QQ1mz1b3yz3PP5; Mon, 22 May 2023 15:38:11 +0000 (UTC) (envelope-from garyj@gmx.de) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.de; s=s31663417; t=1684769889; i=garyj@gmx.de; bh=prZUqIx3zWlzMwCTdLcf0PxyhG8tkaK2BwqbHUzwZ1A=; h=X-UI-Sender-Class:Date:From:To:Cc:Subject:In-Reply-To:References: Reply-To; b=nMddVMfengsCkxPywy93RKDqYND3u5iLXxE10lcxvyqGbHUquHk3iLYAMKp3DPDd7 PW6h3ZgGKNkDLvgWaOWqA/aHwMnHavCHzncpa7iOR1toUtHSHEEGZmaCYXW6ZHz1yL 6nABJbWIaY9n5B6y8lWGMhsV1HpHSYqXyS+S4+TSCm6qkQBW9zMBD+SZ0zjWFLjvWr B2N/PJxnJvBP+TE0KnG4vR7kTvVmXAHVMABCnl2cqcXeO34aiwYAzt2gG1NkN9I43B nSOjRRGdJ9lNIsw9Lt6FhBAc1JlzO5d2WnvE3esBBl3MwO682PT9r22qGlGS3hVC5w gwlMFuzcP9IdQ== X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a Received: from ernst.home ([91.59.238.143]) by mail.gmx.net (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1Mg6e4-1qcwH90IxC-00hhWs; Mon, 22 May 2023 17:38:09 +0200 Date: Mon, 22 May 2023 15:37:53 +0000 From: Gary Jennejohn To: Alexander Chernikov Cc: current@freebsd.org Subject: Re: builworld fails due to error in af_inet.c Message-ID: <20230522173753.7f227dfa@ernst.home> In-Reply-To: <1B5092E2-27AB-45B7-B726-F83B6986638D@FreeBSD.org> References: <20230522170000.25468c5f@ernst.home> <1B5092E2-27AB-45B7-B726-F83B6986638D@FreeBSD.org> Reply-To: garyj@gmx.de X-Mailer: Claws Mail 3.19.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) 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: quoted-printable X-Provags-ID: V03:K1:QlSmOHK5IbgPBtbxn7HSvRL9EgL4VhvIJPFT+yE2y19rTJe3Lvh 6eG2/cLxD0mYhx352JAitdfhZc8oyQcS/EOTZBLck1rovT+HLrYICPA/29IbJCKf2nDXXnn aOpz2Rm/4Vgy3TdKGooceOU3RbE2tPdtwGVP6ovQ+ZKRKwRasCfVKaS/24mFBzpyDXFRaJq 2iyghjzZRXkCwev9nBUFg== X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:CX4Mers8QvA=;HqzxUyIr6QHuzaarauxA98+wP0l T/VSFWMx9b7jZxxS+OB1e0tWhjcLVtyXF1kk88MAxOhAgxrd+7dDTa8agG1MjRK5nX8HUn/Wz P2TnJUT3046+rH7Cd3SnkD175C/t1/elit9o2pQqj93ptkE0kiBbHQFZySBPLnxdJecIX3cne ZkmSiKK98lC8KCk5DaoYt0zpdjJqDZSHmZdHSzIx7uAyhnQsDpWeDoKSbOzxp6kovz1oyvkR/ k+OH/sz58a/lSUNlMlsdl3ZSuaGUt4nOHOojwSSV76m/dN4nBi2CUvkcEQPITs5yjZ57/t05P LSQO4FoHJ4/CZ7nOzh3QBDTDHcM6lQ7bpitaUMirUDq9siN85kxcUqIZ79gPp5NVG7sUGO+62 +bbGf4nN+oHuM85Miyg+gGZVxUHu49wS6XOMO9K4sFg+J2sdvvBb/9znM/aSCuZYvQMqHwpLq AKPo56pii3ujIHaFv2CgbN5RQGmkwAsekGklTvbLNO7HPN3uT7h43i47p44t7nN+JGk6rG35o MEiR5NaEGfJ2AuS3uxO5ZU/LR+rjrUUOz8nSlNr4tkYs3c4xWBxMz3+XE6TB+lT693oKmXy8Z Hr74TU6Ap496HRmz0RQ7zhOcRwpaeZRURQm0Fyfpi62CDoCdNLBEPpLP67mGoFChPnTYDVRoS cxXAnmWh5f2g2fnBq2nEnL+PT8XtFLQKALLEWMwrKpaXa9noNhxOccmrwMtlf8ruuwKEMj3W2 VQr+7oj+B/iP/9ArXn9Ex47cicE1ayLEVZ9MN3HkTou5fm39vfd3eBkEwsEIB87w/UIP4nu4Y QA8QCriWIslP2gbrJ7OBhVKRTIRETqrZLJGLqCCEePXibMomhZs/6yjptayZFmndm0bIHKIMz yG/1qNvYBe2WkAyrKN/E6P+ib8Ld/gmUQFRTXc11a/DXGa+ivlFNcfjLgsk+YVv8K3+w6bS0g nAAVnw== X-Rspamd-Queue-Id: 4QQ1mz1b3yz3PP5 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Mon, 22 May 2023 16:03:37 +0100 Alexander Chernikov wrote: > Sorry for the breakage (and thanks for markj@ for the prompt fix) > No big deal. It was easy to find the cause and temporarily fix it. > > On 22 May 2023, at 16:00, Gary Jennejohn wrote: > > > > I just ran buildworld using the latest current source. > > > > It dies due to this error in line 385 of /usr/src/sbin/ifconfig/af_ine= t.c: > > > > static void > > warn_nomask(ifflags) > > > > The compiler really doesn't like not seeing a type for ifflags and bai= ls > > out as the result. > > > > Strangely enough, in_proc() a few lines later clearly has int ifflags = in > > its list of variables. > > > > Setting ifflags to int in warn_nomask() fixes the build. > > > > Wasn't this compile tested before it was committed? > It was & it didn't yell on my setup. > That's interesting. Maybe I have some different settings. But the error message was the standard one about badly formed prototypes. =2D- Gary Jennejohn From nobody Tue May 23 03:18:24 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 4QQKK63Vzhz4CqJ7 for ; Tue, 23 May 2023 03:18:34 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:7400:8808:123::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4QQKK42dXWz3j26 for ; Tue, 23 May 2023 03:18:31 +0000 (UTC) (envelope-from jamie@catflap.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of jamie@catflap.org designates 2001:19f0:7400:8808:123::1 as permitted sender) smtp.mailfrom=jamie@catflap.org; dmarc=pass (policy=none) header.from=catflap.org X-Catflap-Envelope-From: X-Catflap-Envelope-To: Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [209.250.224.51]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id 34N3IOqN056504 for ; Tue, 23 May 2023 04:18:24 +0100 (BST) (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id 34N3IOaX056503 for freebsd-current@freebsd.org; Tue, 23 May 2023 04:18:24 +0100 (BST) (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <202305230318.34N3IOaX056503@donotpassgo.dyslexicfish.net> Date: Tue, 23 May 2023 04:18:24 +0100 Organization: Dyslexic Fish To: freebsd-current@freebsd.org Subject: MOTD is not created correctly (since 2022/02/18) User-Agent: Heirloom mailx 12.4 7/29/08 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-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [209.250.224.51]); Tue, 23 May 2023 04:18:24 +0100 (BST) X-Spamd-Result: default: False [-3.68 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-0.98)[-0.983]; DMARC_POLICY_ALLOW(-0.50)[catflap.org,none]; R_SPF_ALLOW(-0.20)[+mx:dyslexicfish.net]; MIME_GOOD(-0.10)[text/plain]; RCVD_NO_TLS_LAST(0.10)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; ARC_NA(0.00)[]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; HAS_ORG_HEADER(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FROM_HAS_DN(0.00)[]; FREEFALL_USER(0.00)[jamie]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; ASN(0.00)[asn:20473, ipnet:2001:19f0:7400::/38, country:US] X-Rspamd-Queue-Id: 4QQKK42dXWz3j26 X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N I've just finally updated to 13-stable, and can't be the first to notice this?! /etc/rc.d/motd contains the line: uname -v | sed -e 's,^\([^#]*\) #\(.* [1-2][0-9][0-9][0-9]\).*/\([^\]*\) $,\1 (\3) #\2,' Note the space before the "$" - needed because the uname -v output used to have a trailing space. This was fixed and comitted on 2022/02/18: https://cgit.freebsd.org/src/commit/usr.bin/uname/uname.c?id=7e05fa3b449007adaa6e588ebb3b8d76f30b355c Since then, the sed doesn't match, so the uname(1) output is unchanged. There's no point altering the sed to work with both posibilities, so can someone commit the fix of removing the ' ' before the '$' in /etc/rc.d/motd ? Cheers Jamie From nobody Tue May 23 04:37:40 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 4QQM4Z5hsjz4T0yc for ; Tue, 23 May 2023 04:37:50 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from anubis.delphij.net (anubis.delphij.net [64.62.153.212]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "anubis.delphij.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QQM4Z1yjfz3rRN for ; Tue, 23 May 2023 04:37:50 +0000 (UTC) (envelope-from delphij@delphij.net) Authentication-Results: mx1.freebsd.org; none Received: from odin.corp.delphij.net (c-141-193-140-175.rev.sailinternet.net [141.193.140.175]) by anubis.delphij.net (Postfix) with ESMTPSA id 047C54D443; Mon, 22 May 2023 21:37:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=delphij.net; s=m7e2; t=1684816663; x=1684831063; bh=837mxsOSFCjMEY/7CFx9xY4JWxeCCXaZB0w4/64yWrA=; h=Date:Reply-To:Subject:To:References:From:In-Reply-To; b=wN3PoCpEgrMfPpZRtVudobbBn3u0tSXEOnEqtchcBBYUR5ZYmo7VgfDTJHyvWF8zh vNw1TR0pHnIaFW0FEbmXWp5KJkYrupr5Y8qOWksKKtkfCJMOLVa0vcyIs3kiM59oUY RZnd+TzNkO9EdiblFRBinhUMoflcJefl5pR/jmpVe2XeBxEF7fS9APNmD8ZZOSidr/ ezKo5QUR7H9EHFZejHXs6W3J6pUsEll2YNPYsjaGaghxdAosk9Fv6665Ki323Zm/ML tcNGMO4RIJ6OyA6wlg4lEMezICIrVvhMbDPxMLWcdWFDljegaTPcgxjaBmw8L0pc3R ecPpJLAgkeJaQ== Message-ID: <06086c98-8d54-49b3-d292-d26eb247fcd6@delphij.net> Date: Mon, 22 May 2023 21:37:40 -0700 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: Thunderbird Reply-To: d@delphij.net Subject: Re: MOTD is not created correctly (since 2022/02/18) To: Jamie Landeg-Jones , freebsd-current@freebsd.org References: <202305230318.34N3IOaX056503@donotpassgo.dyslexicfish.net> Content-Language: en-US From: Xin Li In-Reply-To: <202305230318.34N3IOaX056503@donotpassgo.dyslexicfish.net> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------VM16NyQmn7ITvaHKYfj8B4lg" X-Rspamd-Queue-Id: 4QQM4Z1yjfz3rRN X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:6939, ipnet:64.62.128.0/18, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------VM16NyQmn7ITvaHKYfj8B4lg Content-Type: multipart/mixed; boundary="------------0u0cevqZJLJI8iyP9s453HWH"; protected-headers="v1" From: Xin Li Reply-To: d@delphij.net To: Jamie Landeg-Jones , freebsd-current@freebsd.org Message-ID: <06086c98-8d54-49b3-d292-d26eb247fcd6@delphij.net> Subject: Re: MOTD is not created correctly (since 2022/02/18) References: <202305230318.34N3IOaX056503@donotpassgo.dyslexicfish.net> In-Reply-To: <202305230318.34N3IOaX056503@donotpassgo.dyslexicfish.net> --------------0u0cevqZJLJI8iyP9s453HWH Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 T24gMjAyMy0wNS0yMiA4OjE4IFBNLCBKYW1pZSBMYW5kZWctSm9uZXMgd3JvdGU6DQo+IEkn dmUganVzdCBmaW5hbGx5IHVwZGF0ZWQgdG8gMTMtc3RhYmxlLCBhbmQgY2FuJ3QgYmUgdGhl IGZpcnN0IHRvIG5vdGljZSB0aGlzPyENCj4gDQo+IC9ldGMvcmMuZC9tb3RkIGNvbnRhaW5z IHRoZSBsaW5lOg0KPiANCj4gdW5hbWUgLXYgfCBzZWQgLWUgJ3MsXlwoW14jXSpcKSAjXCgu KiBbMS0yXVswLTldWzAtOV1bMC05XVwpLiovXChbXlxdKlwpICQsXDEgKFwzKSAjXDIsJw0K PiANCj4gTm90ZSB0aGUgc3BhY2UgYmVmb3JlIHRoZSAiJCIgLSBuZWVkZWQgYmVjYXVzZSB0 aGUgdW5hbWUgLXYgb3V0cHV0IHVzZWQNCj4gdG8gaGF2ZSBhIHRyYWlsaW5nIHNwYWNlLiBU aGlzIHdhcyBmaXhlZCBhbmQgY29taXR0ZWQgb24gMjAyMi8wMi8xODoNCj4gDQo+IGh0dHBz Oi8vY2dpdC5mcmVlYnNkLm9yZy9zcmMvY29tbWl0L3Vzci5iaW4vdW5hbWUvdW5hbWUuYz9p ZD03ZTA1ZmEzYjQ0OTAwN2FkYWE2ZTU4OGViYjNiOGQ3NmYzMGIzNTVjDQo+IA0KPiBTaW5j ZSB0aGVuLCB0aGUgc2VkIGRvZXNuJ3QgbWF0Y2gsIHNvIHRoZSB1bmFtZSgxKSBvdXRwdXQg aXMgdW5jaGFuZ2VkLg0KPiANCj4gVGhlcmUncyBubyBwb2ludCBhbHRlcmluZyB0aGUgc2Vk IHRvIHdvcmsgd2l0aCBib3RoIHBvc2liaWxpdGllcywgc28gY2FuDQo+IHNvbWVvbmUgY29t bWl0IHRoZSBmaXggb2YgcmVtb3ZpbmcgdGhlICcgJyBiZWZvcmUgdGhlICckJyBpbiAvZXRj L3JjLmQvbW90ZCA/DQoNCk1heWJlIGh0dHBzOi8vcmV2aWV3cy5mcmVlYnNkLm9yZy9ENDAy MjUgPw0KDQooTmljZSBmaW5kIGJ5IHRoZSB3YXkhICBJIGFsd2F5cyBmZWVsIHRoYXQgc29t ZXRoaW5nIHdhcyBub3QgcmlnaHQgYnV0IA0KaGF2ZW4ndCBsb29rZWQgY2xvc2UgZW5vdWdo LikNCg0KQ2hlZXJzLA0K --------------0u0cevqZJLJI8iyP9s453HWH-- --------------VM16NyQmn7ITvaHKYfj8B4lg Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEEceNg5NEMZIki80nQQHl/fJX0g08FAmRsQxQFAwAAAAAACgkQQHl/fJX0g0/z DRAAkiM2CpOD1Y9vCY6SVl8+CkcqESWFCzGa5m3VDXg09unIaQoaDtIWs9KOREKd8fn/+6qNkte0 YXX8fQnp4gHhEfYQ0Itby/Cqx75oxluV/i9+KCBWHX8b2+XU4NSJSf1JGjWh8Ik6QJ31BC0ybcuh 2bisukzL5nhaQ3MiyQwQ6ZrK7PNPRU2Q2Nbsp1DSUrutC/kZDJfAm0em8Je0/shqmBd3E51HV+Ri fLJOfAVsmM+w+Rtxh1abCsTFr5hi20jSHLdH0N7fS1j/A0DEYKGrWEcCUzjrs5M/hbVJgvlnFBO6 ouOKWMZqSOqpeSFkN0kmZAWvMVK6cS2V3PQcdzgQ/5IaQjKQgb0Nvp+nbMOiKtjf/7sSgYxyBtVw YJtgcfa/GpdBtuKmlE1+ZJxi212RfZjCkqR9jN9ekdm2ZXqe0/uiEVWXwT/gzZuMEGoMYMJ2ISFn CgiKFwqGgjJoNpyMuSSD0cMGNV/qOgPR/Wzgoglqf46vdBE2Yt6iL+A9WPm3ffAi3JsdXYg4M2Mc c/Sxr1Iu2ZE9eAcQCt1H76ZK1kOcBfjyhQM2JVAn0ehCqGE96L7KOeNWrwb4yg4YtygBsJQ6jJ4R UI49xf6tqJ7LY5FrV4seRCFgdaHuMhMm7ok8Rapr9mFHBXZFoJFHRKYfdNS63hMqCyWuDJ14Ho34 qv8= =k0dn -----END PGP SIGNATURE----- --------------VM16NyQmn7ITvaHKYfj8B4lg-- From nobody Tue May 23 06:06:08 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 4QQP2Y6vxDz4T6Ls for ; Tue, 23 May 2023 06:06:13 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pg1-x530.google.com (mail-pg1-x530.google.com [IPv6:2607:f8b0:4864:20::530]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QQP2Y4KB0z42cb for ; Tue, 23 May 2023 06:06:13 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pg1-x530.google.com with SMTP id 41be03b00d2f7-51f6461af24so4705862a12.2 for ; Mon, 22 May 2023 23:06:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684821970; x=1687413970; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=c4mpTkkx+36Y5hNPjhEyOgejchh9F7uyViPAHhBRxy0=; b=BzLmK9YLmx4V9wVEnrp5TMaAcSE8eFHnmKytPDYLUUR3za6nS+xeM+JiA1rAksDo4/ BhgcG1D7IdtiV3an2JTOzu1nyvHMqVZAuNL4Z/lN+ccYeU8W4P3teNoDBjngL4Ws4l90 i7I3Grvvq0CE1Cfe4fiK4Ps8pG0NboIh2itOZHgNIVq88+Q6luHon5QTTq91MrK4qWCZ IJl5nD52hrqtLcy0+OAigqYMgCGyFJCsknqzeWaG2d3BASfbGnPqYImtIGkkDtsaioTy OmbAT/3P462QQyKuBwzU5cELuZSCTHsAinaKZdl4TChcVflhZMYg46iPcAAiCIaM+jb9 oOCw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684821970; x=1687413970; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=c4mpTkkx+36Y5hNPjhEyOgejchh9F7uyViPAHhBRxy0=; b=YDuBdzX+lEsCEmsXrKeF5k3uaLpYHvBTHdLBkh6XZorTQBqpxFP9/9JHAm/He4GIY9 eW+L+0KRzIliGjiErLG0RGk1Acmx6u81poKf4MJu26x+6s55anRZcuJcjsQvxHHHkeMH fxzuenAxbWjDkw2DK+KlN9x+Q7JJsyHKluC+PTiUz6jUW8RWxiDIJRB1WPXkPitWMUQB 5+FrYxj5WX2SeslzNEPACBMNbGTzj8Fnxnffk3bFWu1xOCv51hEqBDaeEvv91FO/Qaq0 uWNhSzEqunEEsfPzMJwVWZl9NJrOxO3XJzcYYtlpaNzjCiS+tCE1xc4IN2fcfk7+H0kc n5gQ== X-Gm-Message-State: AC+VfDw6kLScbpV5cQdnUUneAiWXT3/yjBnBPszS3ttJrBG4HjFnc5OG HqEvJSW4EVCES0H0nrOzrbz5jrf7GpIkAw== X-Google-Smtp-Source: ACHHUZ7I3rcUBI7Nnq2eOgiium5tPZRNpCIDNBxi2fI30j8gvlKo+lUIwFSjzrswaR7o/c4cgrq86w== X-Received: by 2002:a17:902:eb46:b0:1ac:9cad:1845 with SMTP id i6-20020a170902eb4600b001ac9cad1845mr13350785pli.18.1684821970214; Mon, 22 May 2023 23:06:10 -0700 (PDT) Received: from smtpclient.apple (c-73-19-52-228.hsd1.wa.comcast.net. [73.19.52.228]) by smtp.gmail.com with ESMTPSA id je3-20020a170903264300b001a9581d3ef5sm5894793plb.97.2023.05.22.23.06.09 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 22 May 2023 23:06:09 -0700 (PDT) Content-Type: multipart/signed; boundary="Apple-Mail=_9AF78CF0-6B76-4B17-AEBB-562F49C176B4"; protocol="application/pgp-signature"; micalg=pgp-sha256 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 (Mac OS X Mail 16.0 \(3696.120.41.1.3\)) Subject: Re: MOTD is not created correctly (since 2022/02/18) From: Enji Cooper In-Reply-To: <202305230318.34N3IOaX056503@donotpassgo.dyslexicfish.net> Date: Mon, 22 May 2023 23:06:08 -0700 Cc: freebsd-current@freebsd.org Message-Id: <1FA0E3FF-9DF6-46BA-81C1-4DCE5542CAD5@gmail.com> References: <202305230318.34N3IOaX056503@donotpassgo.dyslexicfish.net> To: Jamie Landeg-Jones X-Mailer: Apple Mail (2.3696.120.41.1.3) X-Rspamd-Queue-Id: 4QQP2Y4KB0z42cb X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --Apple-Mail=_9AF78CF0-6B76-4B17-AEBB-562F49C176B4 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On May 22, 2023, at 8:18 PM, Jamie Landeg-Jones = wrote: >=20 > I've just finally updated to 13-stable, and can't be the first to = notice this?! >=20 > /etc/rc.d/motd contains the line: >=20 > uname -v | sed -e 's,^\([^#]*\) #\(.* = [1-2][0-9][0-9][0-9]\).*/\([^\]*\) $,\1 (\3) #\2,' >=20 > Note the space before the "$" - needed because the uname -v output = used > to have a trailing space. This was fixed and comitted on 2022/02/18: >=20 > = https://cgit.freebsd.org/src/commit/usr.bin/uname/uname.c?id=3D7e05fa3b449= 007adaa6e588ebb3b8d76f30b355c >=20 > Since then, the sed doesn't match, so the uname(1) output is = unchanged. >=20 > There's no point altering the sed to work with both posibilities, so = can > someone commit the fix of removing the ' ' before the '$' in = /etc/rc.d/motd ? Hi Jamie, Thank you for the note =E2=80=94 could you please file a PR and = reference it in a reply? Thanks! -Enji --Apple-Mail=_9AF78CF0-6B76-4B17-AEBB-562F49C176B4 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEtvtxN6kOllEF3nmX5JFNMZeDGN4FAmRsV9AACgkQ5JFNMZeD GN7PshAAjWKj1sYPmTM3BkILKRihqAgR+ElpBkBL8ElkIOnS8vea8KchdocSd6DN wjouseX6oM4uiiccFurL0WkB98IaZp/Yl6wNVuHMMO5/KbrKbhqWgEtsCvsykvqC gAqcWEidlwKcEng65/9ef+n59hVzS5tT+fRuMLfJzkAEuIHTR4cWVi8/HnODxB8z XkETMWOlTCiLk12DaY2JRCUG/2M3D1ww2LsVQQepJt0cqwNRegfY2xB7Zag6+JU4 RGaIrmjU4JfJlcxBUK/jvpsEQgiKWsYVZnJTixERONTF5W/pZ+ljYcwJ4jUF+P25 xG+8Zm4r3z25wJN7UxMAJeG31IPUU8N9s4to/e5D9DaNH8aG3TChYLTu7OuH3mfi eqUHaoxB0tZVFtg0NpuJ2veC4HRPU17TEIlJEWkjIQ2TG54unENypFSE50+dekbL t5UObylbjOEaXyP8Ia71x3KFuOmCfAjFlM2/RgAcA78Ba8kQOljvsDMZeMXoBTCk /BbJEUwT1rkKBkUahMYYwRtgohN7JU1FGp1qE35mCJh/rpudAE6V792sf0FPsxQB lP8NSTxfod3ogo/URxvZztB7EyBkeODtdKWYf893Wn/oOhtY2I9m/nbHeHQcrpIP Ge66H9IAE+0F5yCTjp4B0Eub/Mzi1hZYxSKrQgbIhrPIEgWf4cM= =QmZa -----END PGP SIGNATURE----- --Apple-Mail=_9AF78CF0-6B76-4B17-AEBB-562F49C176B4-- From nobody Tue May 23 06:06:53 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 4QQP3R2dXgz4T6H6 for ; Tue, 23 May 2023 06:06:59 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pf1-x434.google.com (mail-pf1-x434.google.com [IPv6:2607:f8b0:4864:20::434]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QQP3Q0ghPz43rq for ; Tue, 23 May 2023 06:06:58 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=Ok04AhVR; spf=pass (mx1.freebsd.org: domain of yaneurabeya@gmail.com designates 2607:f8b0:4864:20::434 as permitted sender) smtp.mailfrom=yaneurabeya@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-pf1-x434.google.com with SMTP id d2e1a72fcca58-64a9335a8e7so3018718b3a.0 for ; Mon, 22 May 2023 23:06:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684822015; x=1687414015; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=fAwQj+KB1GmOrO/uyG1HYiqVYAFHZVaMhPnnZZUIDco=; b=Ok04AhVRfuZQFQdNnlTxG+8TeaXL4IHPx+ieLW89WjIWAoPP7F1UcxS7/zt9Ec4oyG A+C5iT+LFDoI5WPNhwWQU3ZIb8OT+wo/neW7w50vqmwjw//s7SMCHcecl67AhoTMROT1 OyyQC7+OOs5YJ/L3bhLIILjcHmyp8veXU3hYrr7jbPHMrmUKZzqvkTYzZpaXXQ+1CGhL FqUqOL3+QjzGpGxdSrN9DCaf+BimIMFPGvGaP7pF7yQaVISICGOWAK2K90WDFXIUzB8U ympWJSspfUcHDAFsQeQTXFCkkVF/cK4CHDKc+byuKbQ/tc8DK1VgnPeSE62h3nN8sx5q OhGg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684822015; x=1687414015; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=fAwQj+KB1GmOrO/uyG1HYiqVYAFHZVaMhPnnZZUIDco=; b=ZHRUzAcGnxZxVK9mLYzVLMIXbA68S8C1HNN2XmF5xWqrMUoJnFHOtd19kCYRpd8ZNu yo7PoPiIuakvraafqHDr/tujYxjeL66/zIgDQO2+rmiMZX6/AchRjZJrApHfQ0SaRU/D fzY81DVZeeOAW2pPWHV3rhrfv3oxZIlEFk2rXR09BxyyXDVsdJAkXuqJcrTFvdCv8CeZ vwwoJkBV/hJSRTp7iF02oQU8C2CdVGaW+5+VKnekj2BYSmIpodnXGpMlRquiArsmEeG6 fyKx1/6/lAePLFBRIO7AOZoWfU4aU/T58udCyjMJSV1oXJXzqUgYHEEIeynL9OH6Edum RfFg== X-Gm-Message-State: AC+VfDyag68xIdRvS/K2x1R1PH8HCejDAAm0X3UAFpLaV/G31agnSMSC tQP0FS6JaLtlOnj5VkvgwDVZtZoKhc7KnQ== X-Google-Smtp-Source: ACHHUZ5gbRgafKPH7lbhoz0p1W7ukqEf/FGMUtrGQtm8x+LxK01Gip45uG51zNEXH7527iIEqg7/vw== X-Received: by 2002:a17:902:da92:b0:1ac:94b3:3ab4 with SMTP id j18-20020a170902da9200b001ac94b33ab4mr18088956plx.27.1684822015264; Mon, 22 May 2023 23:06:55 -0700 (PDT) Received: from smtpclient.apple (c-73-19-52-228.hsd1.wa.comcast.net. [73.19.52.228]) by smtp.gmail.com with ESMTPSA id je3-20020a170903264300b001a9581d3ef5sm5894793plb.97.2023.05.22.23.06.54 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 22 May 2023 23:06:54 -0700 (PDT) From: Enji Cooper Message-Id: Content-Type: multipart/signed; boundary="Apple-Mail=_9248556B-B6EB-43DF-997E-D359F5765F66"; protocol="application/pgp-signature"; micalg=pgp-sha256 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 (Mac OS X Mail 16.0 \(3696.120.41.1.3\)) Subject: Re: MOTD is not created correctly (since 2022/02/18) Date: Mon, 22 May 2023 23:06:53 -0700 In-Reply-To: <1FA0E3FF-9DF6-46BA-81C1-4DCE5542CAD5@gmail.com> Cc: freebsd-current@freebsd.org To: Jamie Landeg-Jones References: <202305230318.34N3IOaX056503@donotpassgo.dyslexicfish.net> <1FA0E3FF-9DF6-46BA-81C1-4DCE5542CAD5@gmail.com> X-Mailer: Apple Mail (2.3696.120.41.1.3) X-Spamd-Result: default: False [-5.51 / 15.00]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.91)[-0.911]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; MIME_GOOD(-0.20)[multipart/signed,multipart/alternative,text/plain]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; ARC_NA(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::434:from]; HAS_ATTACHMENT(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_SOME(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_THREE(0.00)[3]; RCPT_COUNT_TWO(0.00)[2]; DKIM_TRACE(0.00)[gmail.com:+]; MIME_TRACE(0.00)[0:+,1:+,2:+,3:~,4:~]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org] X-Rspamd-Queue-Id: 4QQP3Q0ghPz43rq X-Spamd-Bar: ----- X-ThisMailContainsUnwantedMimeParts: N --Apple-Mail=_9248556B-B6EB-43DF-997E-D359F5765F66 Content-Type: multipart/alternative; boundary="Apple-Mail=_2552AE10-6A8D-4B1A-8C25-3D92120C927E" --Apple-Mail=_2552AE10-6A8D-4B1A-8C25-3D92120C927E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On May 22, 2023, at 11:06 PM, Enji Cooper = wrote: >=20 >>=20 >> On May 22, 2023, at 8:18 PM, Jamie Landeg-Jones = wrote: >>=20 >> I've just finally updated to 13-stable, and can't be the first to = notice this?! >>=20 >> /etc/rc.d/motd contains the line: >>=20 >> uname -v | sed -e 's,^\([^#]*\) #\(.* = [1-2][0-9][0-9][0-9]\).*/\([^\]*\) $,\1 (\3) #\2,' >>=20 >> Note the space before the "$" - needed because the uname -v output = used >> to have a trailing space. This was fixed and comitted on 2022/02/18: >>=20 >> = https://cgit.freebsd.org/src/commit/usr.bin/uname/uname.c?id=3D7e05fa3b449= 007adaa6e588ebb3b8d76f30b355c >>=20 >> Since then, the sed doesn't match, so the uname(1) output is = unchanged. >>=20 >> There's no point altering the sed to work with both posibilities, so = can >> someone commit the fix of removing the ' ' before the '$' in = /etc/rc.d/motd ? >=20 > Hi Jamie, > Thank you for the note =E2=80=94 could you please file a PR and = reference it in a reply? Ah, never mind. I see that it=E2=80=99s been fixed recently on main. -Enji --Apple-Mail=_2552AE10-6A8D-4B1A-8C25-3D92120C927E Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8

On May 22, 2023, at 11:06 PM, Enji Cooper <yaneurabeya@gmail.com> wrote:


On May 22, 2023, at 8:18 PM, Jamie = Landeg-Jones <jamie@catflap.org> wrote:

I've just finally updated to 13-stable, and can't be the = first to notice this?!

/etc/rc.d/motd = contains the line:

uname -v | sed -e = 's,^\([^#]*\) #\(.* [1-2][0-9][0-9][0-9]\).*/\([^\]*\) $,\1 (\3) = #\2,'

Note the space before the "$" - = needed because the uname -v output used
to have a trailing = space. This was fixed and comitted on 2022/02/18:

https://cgit.freebsd.org/src/commit/usr.bin/uname/uname.c?id=3D= 7e05fa3b449007adaa6e588ebb3b8d76f30b355c

Since then, the sed doesn't match, so the uname(1) output is = unchanged.

There's no point altering the = sed to work with both posibilities, so can
someone commit = the fix of removing the ' ' before the '$' in /etc/rc.d/motd ?

Hi Jamie,
= Thank you for = the note =E2=80=94 could you please file a PR and reference it in a = reply?

Ah, never mind. I see that it=E2=80=99s been fixed = recently on main.
-Enji
= --Apple-Mail=_2552AE10-6A8D-4B1A-8C25-3D92120C927E-- --Apple-Mail=_9248556B-B6EB-43DF-997E-D359F5765F66 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEtvtxN6kOllEF3nmX5JFNMZeDGN4FAmRsV/0ACgkQ5JFNMZeD GN4o2xAAiQNac3RUOM/JYASafen9TgXRhS6JmTPYL3EdQrUiaMcRk/l5TQos5PYq mOcJsw05XTviPrSgL6z/44SGbYcsvv5QM8qB2P5mpHqVOV1eT16Jxyo6sha+QGlP oF5p1cRblJsfFX55Iml8uIBlmCpzmAt7OSXaEHfQLfhaNDiN4YSXoSSO5DQLzCoT 4b7BwRP2AQqWDnJTdbqcMnsQWMvO3ZjVj2wgnj9Fl955BiwZaTtCQpoqxelBALTa dhk5Mn4DOwWplqz8ADZxH5Kd1UpgQLb1AoNBvxFdoTUKVc9kZV9S90YMPpxJL3i9 sr99n8DrVzk7t9PB3GJQVwvRWlEy562w60SYZmCq0wRqscsJxiur5vNBNT0vZsM0 Q9QYjEiidTUQlYnpoowRH11TNbu70nzlsoUXAfxmCG/TI8YjtlRnBt1EVt2Q+4wu XofpAeN2cmmY5c7Zwm1rZT75kRot+to3XzB/TNQjtijCZuxHKRmyp0VVLazGDr3C W0YlcQ92jYx73Z8EqmRgF7jeF+GjHNui2z391kPj9RJrTvp70MGhY+jwB4ATCxNO zKiUsXG9FeLnUbWOwFvbrS9OdwzM7514EARV5pz6Xq1VOU6J4rMrpfBy8v26w/uV /YrZ/bVwbDh2MK+/2/gOLt+EYxHhh5kgXYUdGJJz2mbGWt1PMGw= =ELQ+ -----END PGP SIGNATURE----- --Apple-Mail=_9248556B-B6EB-43DF-997E-D359F5765F66-- From nobody Tue May 23 10:36:50 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 4QQW315Rczz4CJjv for ; Tue, 23 May 2023 10:37:01 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:7400:8808:123::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4QQW312mq1z3JTx for ; Tue, 23 May 2023 10:37:01 +0000 (UTC) (envelope-from jamie@catflap.org) Authentication-Results: mx1.freebsd.org; none X-Catflap-Envelope-From: Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [209.250.224.51]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id 34NAaov1069903; Tue, 23 May 2023 11:36:51 +0100 (BST) (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id 34NAaoKu069902; Tue, 23 May 2023 11:36:50 +0100 (BST) (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <202305231036.34NAaoKu069902@donotpassgo.dyslexicfish.net> Date: Tue, 23 May 2023 11:36:50 +0100 Organization: Dyslexic Fish To: yaneurabeya@gmail.com, jamie@catflap.org, freebsd-current@freebsd.org, d@delphij.net Subject: Re: MOTD is not created correctly (since 2022/02/18) References: <202305230318.34N3IOaX056503@donotpassgo.dyslexicfish.net> <06086c98-8d54-49b3-d292-d26eb247fcd6@delphij.net> In-Reply-To: <06086c98-8d54-49b3-d292-d26eb247fcd6@delphij.net> User-Agent: Heirloom mailx 12.4 7/29/08 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-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [209.250.224.51]); Tue, 23 May 2023 11:36:51 +0100 (BST) X-Rspamd-Queue-Id: 4QQW312mq1z3JTx X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:20473, ipnet:2001:19f0:7400::/38, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Xin Li wrote: > Maybe https://reviews.freebsd.org/D40225 ? > > (Nice find by the way! I always feel that something was not right but > haven't looked close enough.) Thanks! What is the best way to report things like this in the future? I'm happy to create a phabricator report, Enji suggested a PR, and previously, Warner said he's happy to accept github pull requests for small changes. Now, I admit I've not yet looked at how to do github pull requests, so that omission is entirely my fault. As for PRs, I've always done that previously, but these days they tend to go unnoticed. And I thought Phabricator was for comitters only. If that's not the case, do I create a review there and add people myself? That has always seemed a bit presumptuous! Or is it a case of create PR/review, and then notify the appropriate mailing list? If so, when is it appropriate to use phabricator over PR, and vice verca? I'm an old dog still used to "send-pr", but I'm happy to learn the new tricks! :-) Cheers, Jamie From nobody Wed May 24 02:10:30 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 4QQvmG4cpyz4TLn8 for ; Wed, 24 May 2023 02:10:38 +0000 (UTC) (envelope-from gad@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QQvmG4BqWz3Gph; Wed, 24 May 2023 02:10:38 +0000 (UTC) (envelope-from gad@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1684894238; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=ULesKFEF4HB1ksq452FajH+p5Ux5cV4Uj88zfF6Ozhw=; b=TC0gkCTHSTAUMHx8YwnK+b4eY/Jm3CYWmibT/6NpVCCYnp0qXy1cRyvUhgSp2iKVxnByVU pG7SSK/B5Fq09FGzZ/xliKxP+ur0mi/xraga5fmLvsKPQaVdfQF3Qkni5toywGaK5/71wh MUqDRXoKV489myhFBsiyLYsVPSO+fdWw7RFfGxs/bIl6a15zFLd1rz9nSMz62NLBIYMD4j 2FVDFA6imJoXNwxktYOT6dbo+/mcJrXHY4FzQtUaz+NCyNV7sgH4P+JUp2fKNkfOjAwODL MYRu02raeou/jD2QJpW2pWrxpWtg9f1Rwq2/AzM8ft/RU3pXlMg6tUlMiJ7hCQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1684894238; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=ULesKFEF4HB1ksq452FajH+p5Ux5cV4Uj88zfF6Ozhw=; b=MXRau+5ZeYyPhiCAYZs31qYXOc2RAbk7jKtdncCiKl3WSUgs7Pk+pQtrYLydn7spqKvx9X TQoRm9NPXLbL0Ja7T3wUZAGKNwrIbk8k86oW2Cek9XnGHB34F+jEoWw/Yk6CywHOkJjyV4 ltrUlQoQkhAs1S3/2EmTaPgC7rlVtap2vUZcw8Ges3lfImUdAEukNDBRJTHrK7OpEK+I8T FGDXD8e3WhEhiWSdrs9N/xHvACZeJIodPQfAGUNQwclhnoXqpUozIZn4BkxyKMrTGBsl61 vGLOCcISfm7JZnIOJfZyGMoPhn69zPHaA7QiZ8VPbPL5LDpewdzdyvvxbzRwiw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1684894238; a=rsa-sha256; cv=none; b=v16OuvsnKfGKBruL11feW8QUqAtn/Ye1ENHjZVgBRe9JgHjhSQf6YAFmzF75+Bj1fSYI0k oegiSCK06udFzXS52cHm9vu4+rvL+UHJ46Ds6jK5SDMlR39nNH9a9B9rM/Rhp+CLBNrP/6 O3GA2uGlK+oXfWxYkn/SZyR1GqShfBZyfMzhNOU5nwWX3HXKH95bI14qe2bSflR0S/zTLM HEA1cpahN5UwKXxNO7dQW3gHPU+uBCUNaKHrzZefOKS/KiDmONihNg69C/977NAQH8vrwU gmIM/wokVlfcJvxLu1il3CFL4HCUAs4tKOoZIY1qrHiNhKxdWsQrDLXc4BN86A== Received: from [128.113.125.11] (cpe-72-224-11-59.nycap.res.rr.com [72.224.11.59]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gad/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4QQvmG251Dzn1t; Wed, 24 May 2023 02:10:38 +0000 (UTC) (envelope-from gad@FreeBSD.org) From: Garance A Drosehn To: Jamie Landeg-Jones Cc: freebsd-current@freebsd.org Subject: Re: MOTD is not created correctly (since 2022/02/18) Date: Tue, 23 May 2023 22:10:30 -0400 X-Mailer: MailMate (1.14r5937) Message-ID: In-Reply-To: <202305230318.34N3IOaX056503@donotpassgo.dyslexicfish.net> References: <202305230318.34N3IOaX056503@donotpassgo.dyslexicfish.net> 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: multipart/alternative; boundary="=_MailMate_025F1A85-250B-4CB7-B6EB-3C2DC3C3949B_=" X-ThisMailContainsUnwantedMimeParts: N --=_MailMate_025F1A85-250B-4CB7-B6EB-3C2DC3C3949B_= Content-Type: text/plain; format=flowed; markup=markdown Content-Transfer-Encoding: quoted-printable On 22 May 2023, at 23:18, Jamie Landeg-Jones wrote: > I've just finally updated to 13-stable, and can't be the first to = > notice this?! > > /etc/rc.d/motd contains the line: > > uname -v | sed -e 's,^\([^#]*\) #\(.* = > [1-2][0-9][0-9][0-9]\).*/\([^\]*\) $,\1 (\3) #\2,' > > Note the space before the "$" - needed because the uname -v output = > used > to have a trailing space. This was fixed and comitted on 2022/02/18: > > https://cgit.freebsd.org/src/commit/usr.bin/uname/uname.c?id=3D7e05fa3b= 449007adaa6e588ebb3b8d76f30b355c > > Since then, the sed doesn't match, so the uname(1) output is = > unchanged. > > There's no point altering the sed to work with both possibilities, so = > can > someone commit the fix of removing the ' ' before the '$' in = > /etc/rc.d/motd ? Not that it helps you much, but I did notice it and have an alternate version of rc.d/motd on my own systems. I had no particular attachment to the earlier format, so my motd starts out by printing the two lines of: ``` -KU 1302505 1302505 -b 18fa15f83c483db67b818e3a48bbb312908754b1 FreeBSD 13.2-STABLE (Garance-13x) #0 -- Fri May 5 17:53:55 EDT 2023 ``` (that first line is the output from ```printf ' -KU %s -b %s\n' "$(uname -KU)" "$(uname -b)"``` ) But I thought that committing that would trigger a bikeshed debate, so I also have an option to produce the output we previously had. And given that no one seemed to be complaining about the "full uname" version, I figured I had an option for that too. And then I thought all these = options were overkill and would trigger and even longer debate, so I never = brought the ideas forward. :) -- = Garance Alistair Drosehn =3D drosih@rpi.edu Lead Developer @rpi and gad@FreeBSD.org Rensselaer Polytechnic Institute; Troy, NY; USA --=_MailMate_025F1A85-250B-4CB7-B6EB-3C2DC3C3949B_= Content-Type: text/html Content-Transfer-Encoding: quoted-printable

On 22 May 2023, at 23:18, Jamie Landeg-Jones wrote:

I've just finally updated to 13-stable, and can't be the = first to notice this?!

/etc/rc.d/motd contains the line:

uname -v | sed -e 's,^([^#]) #(. [1-2][0-9][0-9]= [0-9])./([^]) $,\1 (\3) #\2,'

Note the space before the "$" - needed because = the uname -v output used
to have a trailing space. This was fixed and comitted on 2022/02/18:

https://cgit.freebsd.org/src/commit/usr.bin/uname/uname.c?id=3D= 7e05fa3b449007adaa6e588ebb3b8d76f30b355c

Since then, the sed doesn't match, so the uname(1) output= is unchanged.

There's no point altering the sed to work with both possi= bilities, so can
someone commit the fix of removing the ' ' before the '$' in /etc/rc.d/mo= td ?

Not that it helps you much, but I did notice it and have = an alternate
version of rc.d/motd on my own systems. I had no particular attachment to the earlier format, so my motd starts out by printing the two lines of:

    -KU 1302505 1302505 -b 18fa15f83c483=
db67b818e3a48bbb312908754b1
FreeBSD 13.2-STABLE (Garance-13x) #0 -- Fri May  5 17:53:55 EDT 2023

(that first line is the output from
printf ' -KU %s -b %s\n' "$(uname -KU)"= ; "$(uname -b)"
)

But I thought that committing that would trigger a bikesh= ed debate, so I
also have an option to produce the output we previously had. And given that no one seemed to be complaining about the "full uname" ver= sion, I
figured I had an option for that too. And then I thought all these optio= ns
were overkill and would trigger and even longer debate, so I never brough= t
the ideas forward. :)

-- =
Garance Alistair Drosehn = =3D drosih@rpi.edu
Lead Developer @rpi = and gad@FreeBSD.org
Rensselaer Polytechnic Institut= e; Troy, NY; USA
--=_MailMate_025F1A85-250B-4CB7-B6EB-3C2DC3C3949B_=-- From nobody Wed May 24 11:25:44 2023 X-Original-To: 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 4QR84y2SHrz4CbDN for ; Wed, 24 May 2023 11:25:54 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [107.204.234.170]) (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 4QR84w4y8hz4L3B; Wed, 24 May 2023 11:25:52 +0000 (UTC) (envelope-from david@catwhisker.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of david@catwhisker.org designates 107.204.234.170 as permitted sender) smtp.mailfrom=david@catwhisker.org; dmarc=none Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.17.1/8.15.2) with ESMTP id 34OBPjX2078102; Wed, 24 May 2023 11:25:45 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.17.1/8.17.1/Submit) id 34OBPiW3078101; Wed, 24 May 2023 04:25:44 -0700 (PDT) (envelope-from david) Date: Wed, 24 May 2023 04:25:44 -0700 From: David Wolfskill To: current@freebsd.org Subject: Build failure in usr.sbin/bhyvectl; sources at main-n263112-ad513b4dba3e Message-ID: Reply-To: current@freebsd.org Mail-Followup-To: current@freebsd.org 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: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="h0PnTSOgRIVQZDMp" Content-Disposition: inline X-Spamd-Result: default: False [-0.38 / 15.00]; REPLYTO_EQ_TO_ADDR(5.00)[]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.98)[-0.981]; R_SPF_ALLOW(-0.20)[+ip4:107.204.234.170]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; MLMMJ_DEST(0.00)[current@freebsd.org]; MIME_TRACE(0.00)[0:+,1:+,2:~]; BLOCKLISTDE_FAIL(0.00)[107.204.234.170:server fail]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; ASN(0.00)[asn:7018, ipnet:107.192.0.0/12, country:US]; FROM_HAS_DN(0.00)[]; FREEFALL_USER(0.00)[david]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DMARC_NA(0.00)[catwhisker.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; HAS_REPLYTO(0.00)[current@freebsd.org] X-Rspamd-Queue-Id: 4QR84w4y8hz4L3B X-Spamd-Bar: / X-ThisMailContainsUnwantedMimeParts: N --h0PnTSOgRIVQZDMp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable This is from an in-place source update from main-n263073-634a770a5e16 to main-n263112-ad513b4dba3e: =2E.. Building /common/S4/obj/usr/src/amd64.amd64/lib/libc/tests/stdio/scanf_test Building /common/S4/obj/usr/src/amd64.amd64/usr.bin/ncurses/dump_entry.o Building /common/S4/obj/usr/src/amd64.amd64/usr.bin/mkimg/tests/img-1x1-409= 6-mbr.vhdx Building /common/S4/obj/usr/src/amd64.amd64/cddl/usr.sbin/zfsd/zfsd.full /usr/src/usr.sbin/bhyvectl/bhyvectl.c:2389:24: error: incompatible pointer = types passing 'struct vm_exit *' to parameter of type 'struct vm_run *' [-W= error,-Wincompatible-pointer-types] error =3D vm_run(vcpu, &vmexit); ^~~~~~~ /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/vmmapi.h:158:46: note: p= assing argument to parameter 'vmrun' here int vm_run(struct vcpu *vcpu, struct vm_run *vmrun); ^ 1 error generated. Given that yesterday's update was uneventful, and that src/usr.sbin/bhyvectl/bhyvectl.c has not changed in several days, I'm guessing that perhaps a recent change to a header, possibly involving vmexit, may be at issue here. Peace, david --=20 David H. Wolfskill david@catwhisker.org Folks who wish to control what others do with their bodies are often called "conservative," when they are actually "authoritarian." See https://www.catwhisker.org/~david/publickey.gpg for my public key. --h0PnTSOgRIVQZDMp Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iNUEARYKAH0WIQSr0Kzv+UJRY3wfOii0+6PfV4Ix1AUCZG30OF8UgAAAAAAuAChp c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0QUJE MEFDRUZGOTQyNTE2MzdDMUYzQTI4QjRGQkEzREY1NzgyMzFENAAKCRC0+6PfV4Ix 1EIiAQC9xdRYcIM89PZSiRuJ187LbvYJ6LZDxn6d+DmFYLCAPQD7BYBT2qcG1Si+ CEzlAWfQ15AtkwwvviafWFOj8xJX1gQ= =w87U -----END PGP SIGNATURE----- --h0PnTSOgRIVQZDMp-- From nobody Wed May 24 11:38:48 2023 X-Original-To: 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 4QR8My3QQNz4CZxq for ; Wed, 24 May 2023 11:38:54 +0000 (UTC) (envelope-from yuri@aetern.org) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (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 4QR8My0PCCz4NH6 for ; Wed, 24 May 2023 11:38:54 +0000 (UTC) (envelope-from yuri@aetern.org) Authentication-Results: mx1.freebsd.org; none Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id CC55A3200C9D for ; Wed, 24 May 2023 07:38:51 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Wed, 24 May 2023 07:38:51 -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=fm3; t= 1684928331; x=1685014731; bh=+ntklTsD4a6UwSUwNkP/ayCKJkoXMZoyspJ 5h8p0Kjs=; b=XUZBamHIa0esP+dU6rlHch/msHbLNSLcXRiTxfhH5ktrlKyU8/L XzDKuff9e0ALK6rjW98E+3prUTqqguzfwaDJQZouSraaPxqAX9PutumAaw66Yyoo kwmHF4U0qAe5cdNKzp0YB6GOOErGHRZATRPR/zKXjewQ0IwZYzWBd9jz5aXPZ1I1 ASJwxNfRmD+7kebuFdJQgn6QabK7XQ1kNDlC5cK3sJqTQxAS2WpvpFeyWIhb1Wcm qEsC1bNY6FT+Q/3M5zaiVmFD0qFQhiYtYQamrLZCHcA3PpfCHCI4zrZyfslKqf/X vTkxX/oOm6D1FtOxs89+YbxErvaYZUJ0HhA== 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=1684928331; x= 1685014731; bh=+ntklTsD4a6UwSUwNkP/ayCKJkoXMZoyspJ5h8p0Kjs=; b=Z dz2OgZx9/pKu5F0J2/69l8q9XvdSEhGUJu6Y9GWLOE95scUX+nFTS2a7p4qEEKoc Kv4nCZd6Wsao6WigaDggsfLCyQwYXns14EGXvV8jbxJ1tgHrfznjUf7p/O1TELjR hCyOAKqJKLC4wOcGVQLygImC+zWLDlriHJ39WplENIhwys6pmO0mAZC0BCkI2HTG 8lh2pFwuVzQHBsd0+vY9uXWugfXcWK6Qxur1YuR9cb3rvcQm/Rgr/Akg+7jkP5Sq 71KpY2Dn7nc392q3/A5z59Ew17VagYnKzX8WQLGzNZt4zMaLRumhYKJdjpubsgez V/+OtGAhqIIeU7HBYpWUw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeejhedggedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtje ertddtfeejnecuhfhrohhmpegjuhhrihcuoeihuhhrihesrggvthgvrhhnrdhorhhgqeen ucggtffrrghtthgvrhhnpeegheelveeuhefhgffgteetffeifffhudetudetuedvhedvhf ffvdethfffjeejvdenucffohhmrghinhepfhhrvggvsghsugdrohhrghenucevlhhushht vghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpeihuhhrihesrggvthgvrh hnrdhorhhg X-ME-Proxy: Feedback-ID: i0d79475b:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Wed, 24 May 2023 07:38:50 -0400 (EDT) Message-ID: <864e924a-7d80-7e6a-11c1-636458ea0c9e@aetern.org> Date: Wed, 24 May 2023 13:38:48 +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.10.1 Subject: Re: Build failure in usr.sbin/bhyvectl; sources at main-n263112-ad513b4dba3e Content-Language: en-US To: current@freebsd.org References: From: Yuri In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4QR8My0PCCz4NH6 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N David Wolfskill wrote: > This is from an in-place source update from main-n263073-634a770a5e16 to > main-n263112-ad513b4dba3e: > > ... > Building /common/S4/obj/usr/src/amd64.amd64/lib/libc/tests/stdio/scanf_test > Building /common/S4/obj/usr/src/amd64.amd64/usr.bin/ncurses/dump_entry.o > Building /common/S4/obj/usr/src/amd64.amd64/usr.bin/mkimg/tests/img-1x1-4096-mbr.vhdx > Building /common/S4/obj/usr/src/amd64.amd64/cddl/usr.sbin/zfsd/zfsd.full > /usr/src/usr.sbin/bhyvectl/bhyvectl.c:2389:24: error: incompatible pointer types passing 'struct vm_exit *' to parameter of type 'struct vm_run *' [-Werror,-Wincompatible-pointer-types] > error = vm_run(vcpu, &vmexit); > ^~~~~~~ > /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/vmmapi.h:158:46: note: passing argument to parameter 'vmrun' here > int vm_run(struct vcpu *vcpu, struct vm_run *vmrun); > ^ > 1 error generated. > > > Given that yesterday's update was uneventful, and that > src/usr.sbin/bhyvectl/bhyvectl.c has not changed in several days, > I'm guessing that perhaps a recent change to a header, possibly > involving vmexit, may be at issue here. https://lists.freebsd.org/archives/dev-commits-src-all/2023-May/026954.html From nobody Wed May 24 11:39:26 2023 X-Original-To: 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 4QR8Nt6md8z4CZy8 for ; Wed, 24 May 2023 11:39:42 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QR8Nt6DkSz4PRV; Wed, 24 May 2023 11:39:42 +0000 (UTC) (envelope-from dim@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1684928382; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=XbB+vqIUVN3dAwW8daZigjt/9RJU2iAmm5JTFlP7ag4=; b=KORjiaEBprAN87O/vK8ckv/sbeWD69Z7qDcHTkwV4OnUyEHYSsGgwimYoNlsosVlkJKLh3 BsrpPSADdvXMCNo2nSIieCSWGjnsKUS73DxyLEDAxEvLPYGLK7yI5dU0S++dWwseWoBFAS bH9mzNFjM+aKD/3mLTE1mMhNI5djGg3OGtSQkctcy8BYe8jL1SgqeJ/4HaGJi404NNKWWd DlQ+iG89bvUpvGhTfHvAAq9CBUUSZeLatDWrN6UiltwEFDvBmMiQAeV3vtrTar9MPca3hg zDs9NurqUnI1OynbiFJthlOfgaxa0IjdieSIOevHqq2GYmRnLEPppnHft5WOrA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1684928382; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=XbB+vqIUVN3dAwW8daZigjt/9RJU2iAmm5JTFlP7ag4=; b=lPy29uOR94mairSw73e/y/eHx14BSGmdIZHcZS7HtyqR33oPomC12FOGLejDb3iLVOva4+ C1p5O1cUNvUKBTxRPjJjnmORrGU0VzRbrZCRZHtgH0EFpY96k/fZFgJVNZ2tpmtAZ80xrt Khn6iZVWK4j0GUAczw8SF2qj/Ef8KCXWb3o3LXslCDunb8yxvfJYyxWaNfiJbUEK7Npz/F ILoUXGD8G8rLNY65MCyQ/uw4Ji321nqXtYU8vjI49yCg+2fbMRy6JhhqiHawfGieJoCSS7 vTbnOhmzcqt0ZCkDIoIVuMLt+Yljod3jRds+63KOC/SyrLhyg5+nOPhkjD0XdA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1684928382; a=rsa-sha256; cv=none; b=xSEdD1C1rRGeu70D1hC5pKG8Eq+xnrnya7PfF9i1aFQJc9mL+OFWPP87SRCUlm9uqWXfjy 2TrPbtdqVnB/BU1t4kL8vGQO72XlXRoP44Sok6RYaLhB4aikLZRkwjSbeGCtehAyRUbmIh NTZ1vjbTHvb/gU/XMSHs80UTnvwqVf3BhTofW3x49KZctcvzHp1zdame3U71kraQUhHNuY wakq47moJf7DSPlLSlBDQGupmI6UG+rbuHLGicpeuAYV6fMjx1Us1H37xbuf0010yZpCSj iu3eM8yhOZ7OK2wHrnu0H0egEgAag/pNJlGOg7begk/mRrXTAhhfaPAfE5FGjQ== Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "tensor.andric.com", Issuer "R3" (verified OK)) (Authenticated sender: dim) by smtp.freebsd.org (Postfix) with ESMTPSA id 4QR8Nt4Z1nzys5; Wed, 24 May 2023 11:39:42 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from smtpclient.apple (longrow.home.andric.com [192.168.0.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 8400719A9; Wed, 24 May 2023 13:39:41 +0200 (CEST) Content-Type: multipart/signed; boundary="Apple-Mail=_A4F262A7-FAE9-4EA2-A4A1-58635A431398"; protocol="application/pgp-signature"; micalg=pgp-sha1 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 (Mac OS X Mail 16.0 \(3731.600.7\)) Subject: Re: Build failure in usr.sbin/bhyvectl; sources at main-n263112-ad513b4dba3e From: Dimitry Andric In-Reply-To: Date: Wed, 24 May 2023 13:39:26 +0200 Cc: Mark Johnston Message-Id: <60EE10D6-1D12-494B-B51C-B81CAF537EF9@FreeBSD.org> References: To: current@freebsd.org X-Mailer: Apple Mail (2.3731.600.7) X-ThisMailContainsUnwantedMimeParts: N --Apple-Mail=_A4F262A7-FAE9-4EA2-A4A1-58635A431398 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 24 May 2023, at 13:25, David Wolfskill wrote: >=20 > This is from an in-place source update from main-n263073-634a770a5e16 = to > main-n263112-ad513b4dba3e: >=20 > ... > Building = /common/S4/obj/usr/src/amd64.amd64/lib/libc/tests/stdio/scanf_test > Building = /common/S4/obj/usr/src/amd64.amd64/usr.bin/ncurses/dump_entry.o > Building = /common/S4/obj/usr/src/amd64.amd64/usr.bin/mkimg/tests/img-1x1-4096-mbr.vh= dx > Building = /common/S4/obj/usr/src/amd64.amd64/cddl/usr.sbin/zfsd/zfsd.full > /usr/src/usr.sbin/bhyvectl/bhyvectl.c:2389:24: error: incompatible = pointer types passing 'struct vm_exit *' to parameter of type 'struct = vm_run *' [-Werror,-Wincompatible-pointer-types] > error =3D vm_run(vcpu, &vmexit); > ^~~~~~~ > /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/vmmapi.h:158:46: = note: passing argument to parameter 'vmrun' here > int vm_run(struct vcpu *vcpu, struct vm_run *vmrun); > ^ > 1 error generated. >=20 >=20 > Given that yesterday's update was uneventful, and that > src/usr.sbin/bhyvectl/bhyvectl.c has not changed in several days, > I'm guessing that perhaps a recent change to a header, possibly > involving vmexit, may be at issue here. It appears to be broken since "vmm: Avoid embedding cpuset_t ioctl = ABIs": = https://cgit.freebsd.org/src/commit/?id=3De17eca327633efc511450310afb5e4a6= 62724e3d See also https://ci.freebsd.org/job/FreeBSD-main-amd64-build/, where it = shows an error since = https://ci.freebsd.org/job/FreeBSD-main-amd64-build/26653/ -Dimitry --Apple-Mail=_A4F262A7-FAE9-4EA2-A4A1-58635A431398 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCZG33bgAKCRCwXqMKLiCW o3WkAKCgc9U6MXmRXZAQ2n/upPeL2GGd3QCfZm4zlxFeFGrDC7GimJkH1Byfy8E= =3Llr -----END PGP SIGNATURE----- --Apple-Mail=_A4F262A7-FAE9-4EA2-A4A1-58635A431398-- From nobody Wed May 24 12:27:46 2023 X-Original-To: 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 4QR9SS20N8z4CfWJ for ; Wed, 24 May 2023 12:27:52 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-il1-x12a.google.com (mail-il1-x12a.google.com [IPv6:2607:f8b0:4864:20::12a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QR9SR3bK1z3FQ5; Wed, 24 May 2023 12:27:51 +0000 (UTC) (envelope-from markjdb@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-il1-x12a.google.com with SMTP id e9e14a558f8ab-3382dc7d50bso5752305ab.2; Wed, 24 May 2023 05:27:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684931269; x=1687523269; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:from:to:cc:subject:date:message-id :reply-to; bh=z5MSxoPB5vFexC9dAWXMNfmxKRJRd5ccui+JYCECuuY=; b=gMgHp+MJxRPTjihmXVqjulgQYrlpjLEDC7Fy9IhJgw6LxT4MAk/R0dBKnKdbOvCZLO A47usZm/hgXyyipZ2+1myFpyqapMzuybCsSF1maSI5vlsrBQ8bFZ8IRdf0KxCArsN+2I p85g0mq1YD+exWvzbp6VLciDqqf+/uDUxEiOylwtwoc8GenwcDN52igt0NcEJVEB6JtZ 4rXQ5/c/2eaQGQ98ycj8zye1HwpEjbi7Zum0LibtLHjL/lcMBHl+JwgzNWE6YTYa2KO8 pTX5Dv/ey2+p0TPq1+wG49G9rZilm9mKmQpZAq+BqM9QUFieU6edKI4JPvSM2+dkjJrP zn+Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684931269; x=1687523269; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=z5MSxoPB5vFexC9dAWXMNfmxKRJRd5ccui+JYCECuuY=; b=da1dSyXCs5yKt40OGbT4pHczEax4Yz90Fqls9lDYyNbBwOioxOeEv7vQEOUgoTuc05 BpA3u3FXWfv36Vr0DGmKcnsk/s0lvgq3H3AVHhyhgsXzZC7yCxD65CN1Y+RMzgaVcNMy WDAL4dq0VPWyhy4T94hznLckCk+Ha72rbbUszmB5nTkRkcNl0CgFLz/9O2IbLZxXqYJs 8VmPAhnpNJ/P63v5fiOQ8iFTv+7Uz1LzQPd0BwFI+E+iZE1wapuY+l2WVZGRYAumLUt6 MlRFmfHPGJ1u3J3v6SfIZAP1fhBXzXhkr6DAppzwScLJwj8LYpZEQI06nOqtxZfdYdOL Muqw== X-Gm-Message-State: AC+VfDxgy987fQRoGqYHIUfzyO6MokH5/G6yfNGYNWL277r/D8iU5ScK 5Yk06AC48cS1aWiWupph2eOQPagpLNA= X-Google-Smtp-Source: ACHHUZ4P/BuV9T90JFCqOSv8ECB++Ab2pcKCyFkNUaP8j/tN01UzOKObxJITNSUrSLJIXKN95puc4g== X-Received: by 2002:a92:cb4a:0:b0:335:542b:aa48 with SMTP id f10-20020a92cb4a000000b00335542baa48mr12585407ilq.19.1684931269538; Wed, 24 May 2023 05:27:49 -0700 (PDT) Received: from nuc (192-0-220-237.cpe.teksavvy.com. [192.0.220.237]) by smtp.gmail.com with ESMTPSA id m16-20020a92d710000000b0032e1f94be7bsm2967804iln.33.2023.05.24.05.27.48 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 24 May 2023 05:27:48 -0700 (PDT) Date: Wed, 24 May 2023 08:27:46 -0400 From: Mark Johnston To: Dimitry Andric Cc: current@freebsd.org Subject: Re: Build failure in usr.sbin/bhyvectl; sources at main-n263112-ad513b4dba3e Message-ID: References: <60EE10D6-1D12-494B-B51C-B81CAF537EF9@FreeBSD.org> 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-Disposition: inline In-Reply-To: <60EE10D6-1D12-494B-B51C-B81CAF537EF9@FreeBSD.org> X-Rspamd-Queue-Id: 4QR9SR3bK1z3FQ5 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Wed, May 24, 2023 at 01:39:26PM +0200, Dimitry Andric wrote: > On 24 May 2023, at 13:25, David Wolfskill wrote: > > > > This is from an in-place source update from main-n263073-634a770a5e16 to > > main-n263112-ad513b4dba3e: > > > > ... > > Building /common/S4/obj/usr/src/amd64.amd64/lib/libc/tests/stdio/scanf_test > > Building /common/S4/obj/usr/src/amd64.amd64/usr.bin/ncurses/dump_entry.o > > Building /common/S4/obj/usr/src/amd64.amd64/usr.bin/mkimg/tests/img-1x1-4096-mbr.vhdx > > Building /common/S4/obj/usr/src/amd64.amd64/cddl/usr.sbin/zfsd/zfsd.full > > /usr/src/usr.sbin/bhyvectl/bhyvectl.c:2389:24: error: incompatible pointer types passing 'struct vm_exit *' to parameter of type 'struct vm_run *' [-Werror,-Wincompatible-pointer-types] > > error = vm_run(vcpu, &vmexit); > > ^~~~~~~ > > /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/vmmapi.h:158:46: note: passing argument to parameter 'vmrun' here > > int vm_run(struct vcpu *vcpu, struct vm_run *vmrun); > > ^ > > 1 error generated. > > > > > > Given that yesterday's update was uneventful, and that > > src/usr.sbin/bhyvectl/bhyvectl.c has not changed in several days, > > I'm guessing that perhaps a recent change to a header, possibly > > involving vmexit, may be at issue here. > > It appears to be broken since "vmm: Avoid embedding cpuset_t ioctl ABIs": > https://cgit.freebsd.org/src/commit/?id=e17eca327633efc511450310afb5e4a662724e3d > > See also https://ci.freebsd.org/job/FreeBSD-main-amd64-build/, where it shows an error since https://ci.freebsd.org/job/FreeBSD-main-amd64-build/26653/ This should be fixed now. My apologies, I had no idea bhyvectl provided a way to run a VM... From nobody Wed May 24 22:32:45 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 4QRQtT1zpnz4V5XN for ; Wed, 24 May 2023 22:32:49 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:7400:8808:123::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4QRQtS64l6z3LHC; Wed, 24 May 2023 22:32:48 +0000 (UTC) (envelope-from jamie@catflap.org) Authentication-Results: mx1.freebsd.org; none X-Catflap-Envelope-From: Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [209.250.224.51]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id 34OMWjUK043289; Wed, 24 May 2023 23:32:45 +0100 (BST) (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id 34OMWjZe043288; Wed, 24 May 2023 23:32:45 +0100 (BST) (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <202305242232.34OMWjZe043288@donotpassgo.dyslexicfish.net> Date: Wed, 24 May 2023 23:32:45 +0100 Organization: Dyslexic Fish To: jamie@catflap.org, gad@FreeBSD.org Cc: freebsd-current@FreeBSD.org Subject: Re: MOTD is not created correctly (since 2022/02/18) References: <202305230318.34N3IOaX056503@donotpassgo.dyslexicfish.net> In-Reply-To: User-Agent: Heirloom mailx 12.4 7/29/08 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-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [209.250.224.51]); Wed, 24 May 2023 23:32:45 +0100 (BST) X-Rspamd-Queue-Id: 4QRQtS64l6z3LHC X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:20473, ipnet:2001:19f0:7400::/38, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Garance A Drosehn wrote: > Not that it helps you much, but I did notice it and have an alternate > version of rc.d/motd on my own systems. I had no particular attachment > to the earlier format, so my motd starts out by printing the two lines > of: > ``` > -KU 1302505 1302505 -b 18fa15f83c483db67b818e3a48bbb312908754b1 > FreeBSD 13.2-STABLE (Garance-13x) #0 -- Fri May 5 17:53:55 EDT 2023 I too was actually not all that fussed with the old style, but the multiple spaces in the output bugged me, so I was going to change it back, when I stumbled on the issue. I actually have closer to yours in my ssh-banner: ****************** ****************** FreeBSD/amd64 13.2-STABLE - Build 1302505 (May 13, 2023) 23:25 BST up 1 01:30 0.16, 0.18, 0.16 -- SOD OFF IF YOU AREN'T AUTHORISED **************************************************************** > But I thought that committing that would trigger a bikeshed debate, so I > also have an option to produce the output we previously had. And given > that no one seemed to be complaining about the "full uname" version, I > figured I had an option for that too. And then I thought all these > options > were overkill and would trigger and even longer debate, so I never > brought > the ideas forward. :) :-) Oh yeah, definitely! It would be worse than the fractional seconds in sleep(1) debate! Cheers, for the response, Jamie From nobody Fri May 26 17:35:23 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 4QSXBH6KkXz4ChKX for ; Fri, 26 May 2023 17:35:19 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QSXBG2ZPzz485f for ; Fri, 26 May 2023 17:35:18 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net; dmarc=none Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.17.1/8.15.2) with ESMTPS id 34QHZOvP029053 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 26 May 2023 10:35:24 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.17.1/8.15.2/Submit) id 34QHZO0w029052; Fri, 26 May 2023 10:35:24 -0700 (PDT) (envelope-from fbsd) Date: Fri, 26 May 2023 10:35:23 -0700 From: bob prohaska To: freebsd-current@freebsd.org Cc: bob prohaska Subject: Surprise null root password Message-ID: 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-Disposition: inline X-Spamd-Result: default: False [-1.02 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-1.00)[-0.997]; NEURAL_HAM_SHORT(-0.99)[-0.993]; NEURAL_HAM_MEDIUM(-0.93)[-0.931]; MID_RHS_WWW(0.50)[]; WWW_DOT_DOMAIN(0.50)[]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; R_DKIM_NA(0.00)[]; R_SPF_NA(0.00)[no SPF record]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_COUNT_THREE(0.00)[3]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[zefox.net]; TO_DN_SOME(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4QSXBG2ZPzz485f X-Spamd-Bar: - X-ThisMailContainsUnwantedMimeParts: N While going through normal security email from a Pi2 running -current I was disturbed to find: Checking for passwordless accounts: root::0:0::0:0:Charlie &:/root:/bin/sh The machine had locked up on a -j4 buildworld since sending the mail, so it was taken off the net, power cycled and started single-user. Sure enough, /etc/master.passwd contained a null password for root, but the last modification to the file was two weeks ago according to ls -l. Stranger still, when fsck'd and brought up multi-user, the normal password was still honored and a null password rejected for both regular and root account. AFAIK, /etc/master.passwd is _the_ password repository, but clearly I'm wrong. If somebody can tell me what's going on and what to check for before placing the machine back on line it would be much appreciated. Thanks for reading, bob prohaska From nobody Fri May 26 18:03:19 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 4QSXpg5qF1z4Ck8X for ; Fri, 26 May 2023 18:03:23 +0000 (UTC) (envelope-from mike@karels.net) Received: from mail2.karels.net (mail2.karels.net [3.19.118.201]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "freebsd", Issuer "freebsd" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QSXpg3rmgz4F4t for ; Fri, 26 May 2023 18:03:23 +0000 (UTC) (envelope-from mike@karels.net) Authentication-Results: mx1.freebsd.org; none Received: from mail2.karels.net (localhost [IPv6:0:0:0:0:0:0:0:1]) by mail2.karels.net (8.17.1/8.17.1) with ESMTP id 34QI3K2D068170; Fri, 26 May 2023 13:03:20 -0500 (CDT) (envelope-from mike@karels.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=karels.net; s=mail2; t=1685124200; bh=BM1HRnPB5h6DYkMO3dzJgHEB0YVpV/ifxvBK0Ep2WTg=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=CDlLE3BtwSqayYxhK8uai57iWdmTQBaYist9i3scYAfXRBEemBiLrrBnAh36lNAYI smuSVrl2XBxlmqnkhZZHu7n3D4ZTbYM4TwR73+63Bf3efKDbHsftsqSOavE5OIURNo uU1kRcSkDwuDKzgfM3zaLLw8w7S5qpJGVLKC0WQCu2FHnonEGqVxL38JRTQbZDx6IX c1uqs3GH++M+ZRhAXYN1gdQa17i+f5D49Ds1zUb1MMqGWdDHOIJuvS75CcCGPk5vbb i7YuDR/UzBykDiau4ofE/fHqSSMIlFiVsuR7nFpY0FpPU1bUuxNKVwVGgWdTQ6BaD9 hrUdjHLwIvgxg== Received: from [10.0.2.130] ([73.62.165.147]) by mail2.karels.net with ESMTPSA id 9EQ0H2j0cGRICgEAs/W3XQ (envelope-from ); Fri, 26 May 2023 13:03:20 -0500 From: Mike Karels To: bob prohaska Cc: freebsd-current@freebsd.org Subject: Re: Surprise null root password Date: Fri, 26 May 2023 13:03:19 -0500 X-Mailer: MailMate (1.14r5964) Message-ID: <945C9B6D-F2A8-4F0D-BDB0-49A3DE870168@karels.net> In-Reply-To: References: 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=UTF-8 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4QSXpg3rmgz4F4t X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:16509, ipnet:3.16.0.0/14, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On 26 May 2023, at 12:35, bob prohaska wrote: > While going through normal security email from a Pi2 > running -current I was disturbed to find: > > Checking for passwordless accounts: > root::0:0::0:0:Charlie &:/root:/bin/sh > > The machine had locked up on a -j4 buildworld since > sending the mail, so it was taken off the net, power > cycled and started single-user. > > Sure enough, /etc/master.passwd contained a > null password for root, but the last modification > to the file was two weeks ago according to ls -l. > > Stranger still, when fsck'd and brought up multi-user, > the normal password was still honored and a null > password rejected for both regular and root account. > > AFAIK, /etc/master.passwd is _the_ password repository, > but clearly I'm wrong. /etc/master.passwd is the source, but the operational database is /etc/spwd.db. You should check the date on it as well. You can rebuild it with “pwd_mkdb -p /etc/master.passwd”. Mike > If somebody can tell me what's going on and what to > check for before placing the machine back on line > it would be much appreciated. > > Thanks for reading, > > bob prohaska From nobody Fri May 26 18:45:08 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 4QSYkf1j6Hz4Clxv for ; Fri, 26 May 2023 18:44:58 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QSYkd7412z4Jl2 for ; Fri, 26 May 2023 18:44:57 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Authentication-Results: mx1.freebsd.org; none Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.17.1/8.15.2) with ESMTPS id 34QIj9a1029169 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 26 May 2023 11:45:09 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.17.1/8.15.2/Submit) id 34QIj8bT029168; Fri, 26 May 2023 11:45:08 -0700 (PDT) (envelope-from fbsd) Date: Fri, 26 May 2023 11:45:08 -0700 From: bob prohaska To: Mike Karels Cc: freebsd-current@freebsd.org Subject: Re: Surprise null root password Message-ID: References: <945C9B6D-F2A8-4F0D-BDB0-49A3DE870168@karels.net> 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-Disposition: inline In-Reply-To: <945C9B6D-F2A8-4F0D-BDB0-49A3DE870168@karels.net> X-Rspamd-Queue-Id: 4QSYkd7412z4Jl2 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Fri, May 26, 2023 at 01:03:19PM -0500, Mike Karels wrote: > On 26 May 2023, at 12:35, bob prohaska wrote: > > > While going through normal security email from a Pi2 > > running -current I was disturbed to find: > > > > Checking for passwordless accounts: > > root::0:0::0:0:Charlie &:/root:/bin/sh > > [details snipped] > /etc/master.passwd is the source, but the operational database > is /etc/spwd.db. You should check the date on it as well. > You can rebuild it with ???pwd_mkdb -p /etc/master.passwd???. At present the host reports: root@www:/usr/src # ls -l /etc/*p*wd* -rw------- 1 root wheel 2099 May 10 17:20 /etc/master.passwd -rw-r--r-- 1 root wheel 1831 May 10 17:20 /etc/passwd -rw-r--r-- 1 root wheel 40960 May 10 17:20 /etc/pwd.db -rw------- 1 root wheel 40960 May 10 17:20 /etc/spwd.db /etc/master.passwd reports a null password for root, /etc/passwd has the usual asterisk. The running system reports root@www:/usr/src # uname -a FreeBSD www.zefox.com 14.0-CURRENT FreeBSD 14.0-CURRENT #25 main-743516d51f: Thu May 18 00:08:40 PDT 2023 bob@www.zefox.com:/usr/obj/usr/src/arm.armv7/sys/GENERIC arm root@www:/usr/src # uname -KU 1400088 1400088 I've never manually run pwd_mkdb and most certainly never set a null password for root. It looks rather as if a null password was set for root within one minute after running pwd_mkdb. At this point I'm unsure how to sort out what happened. The obvious next step is to re-establish a non-null root password and rebuild both databases. Is it worthwhile to check for backdoors? There's no evidence to suggest any malicious action (and plenty of stupidity on my end) but the tale is getting curiouser and curiouser. Many thanks for the quick reply! bob prohaska From nobody Fri May 26 18:48:04 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 4QSYpT2KF3z4CmP8 for ; Fri, 26 May 2023 18:48:17 +0000 (UTC) (envelope-from benlaurie@gmail.com) Received: from mail-ot1-f49.google.com (mail-ot1-f49.google.com [209.85.210.49]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QSYpS6xFrz4KWg for ; Fri, 26 May 2023 18:48:16 +0000 (UTC) (envelope-from benlaurie@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ot1-f49.google.com with SMTP id 46e09a7af769-6af7e368bb7so503672a34.1 for ; Fri, 26 May 2023 11:48:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685126896; x=1687718896; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Z3ssDFo27GDvsTv1+lmp3ABxBi+rrB4uUt3pTCTEoms=; b=XLkaMfsYLfxQlZONaGqmcBCoFPKbUEwty2OEcFBvNPaTHYezulMzP5XNp/60Pc6EDl O7R31iQ+gZJfEVHExlk4MmlzUQx+0fL1tJkLrMtQjjBm0Z4ogwZMwMqnPxsfgOjsEtq+ 6PKCs0H5L624v+qCPjXkXMeAVjCB60Qb+Ag4sFop7ydg0mL9AMDwzyIi6PsE7Cb18sVQ z23N3VK7XXGLb+nR8hAOIQSixAvCffo2UcJdw5YH13Xi5yblWiQA4yojEm/WzVD8DN2p gFzG0wvpZC37fgKWs+R2sUlTnAOLFvzyO+xfLmvgWw+mpGA2TJryGTzxZMw4HOMQqm/i Os9Q== X-Gm-Message-State: AC+VfDz5wkbbIzhZwixfvqaghapGuvh2e1xKJeofFKXTKJulUGUCQvJT HVsUl63IVExNfhgO7lMeGa46ojCJLvFuSUSA7rHJpSGKgm4= X-Google-Smtp-Source: ACHHUZ4eGLfGKbK5diX+vDhntNs67J6mbF3wGpTy8Ty5LTleOgR+qxCA3+2mzBUlxa97zktW+1kvOrE+xsi/ArgOlMg= X-Received: by 2002:a05:6808:2205:b0:398:4651:e06a with SMTP id bd5-20020a056808220500b003984651e06amr1715942oib.46.1685126895927; Fri, 26 May 2023 11:48:15 -0700 (PDT) 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 References: <945C9B6D-F2A8-4F0D-BDB0-49A3DE870168@karels.net> In-Reply-To: From: Ben Laurie Date: Fri, 26 May 2023 19:48:04 +0100 Message-ID: Subject: Re: Surprise null root password To: bob prohaska Cc: Mike Karels , freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="00000000000008876b05fc9d2ed3" X-Rspamd-Queue-Id: 4QSYpS6xFrz4KWg X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --00000000000008876b05fc9d2ed3 Content-Type: text/plain; charset="UTF-8" -T on ls will give you full time resolution... On Fri, 26 May 2023 at 19:45, bob prohaska wrote: > On Fri, May 26, 2023 at 01:03:19PM -0500, Mike Karels wrote: > > On 26 May 2023, at 12:35, bob prohaska wrote: > > > > > While going through normal security email from a Pi2 > > > running -current I was disturbed to find: > > > > > > Checking for passwordless accounts: > > > root::0:0::0:0:Charlie &:/root:/bin/sh > > > > [details snipped] > > /etc/master.passwd is the source, but the operational database > > is /etc/spwd.db. You should check the date on it as well. > > You can rebuild it with ???pwd_mkdb -p /etc/master.passwd???. > > At present the host reports: > root@www:/usr/src # ls -l /etc/*p*wd* > -rw------- 1 root wheel 2099 May 10 17:20 /etc/master.passwd > -rw-r--r-- 1 root wheel 1831 May 10 17:20 /etc/passwd > -rw-r--r-- 1 root wheel 40960 May 10 17:20 /etc/pwd.db > -rw------- 1 root wheel 40960 May 10 17:20 /etc/spwd.db > > /etc/master.passwd reports a null password for root, /etc/passwd > has the usual asterisk. The running system reports > root@www:/usr/src # uname -a > FreeBSD www.zefox.com 14.0-CURRENT FreeBSD 14.0-CURRENT #25 > main-743516d51f: Thu May 18 00:08:40 PDT 2023 bob@www.zefox.com:/usr/obj/usr/src/arm.armv7/sys/GENERIC > arm > root@www:/usr/src # uname -KU > 1400088 1400088 > > I've never manually run pwd_mkdb and most certainly > never set a null password for root. It looks rather > as if a null password was set for root within one > minute after running pwd_mkdb. > > At this point I'm unsure how to sort out what happened. > The obvious next step is to re-establish a non-null > root password and rebuild both databases. > > Is it worthwhile to check for backdoors? There's no > evidence to suggest any malicious action (and plenty > of stupidity on my end) but the tale is getting > curiouser and curiouser. > > Many thanks for the quick reply! > > bob prohaska > > > > > --00000000000008876b05fc9d2ed3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
-T on ls will give you full time resolution...

On Fri, 26 M= ay 2023 at 19:45, bob prohaska <fb= sd@www.zefox.net> wrote:
On Fri, May 26, 2023 at 01:03:19PM -0500, Mike Karels wrote= :
> On 26 May 2023, at 12:35, bob prohaska wrote:
>
> > While going through normal security email from a Pi2
> > running -current I was disturbed to find:
> >
> > Checking for passwordless accounts:
> > root::0:0::0:0:Charlie &:/root:/bin/sh
> >
[details snipped]
> /etc/master.passwd is the source, but the operational database
> is /etc/spwd.db.=C2=A0 You should check the date on it as well.
> You can rebuild it with ???pwd_mkdb -p /etc/master.passwd???.

At present the host reports:
root@www:/usr/src # ls -l /etc/*p*wd*
-rw-------=C2=A0 1 root=C2=A0 wheel=C2=A0 =C2=A02099 May 10 17:20 /etc/mast= er.passwd
-rw-r--r--=C2=A0 1 root=C2=A0 wheel=C2=A0 =C2=A01831 May 10 17:20 /etc/pass= wd
-rw-r--r--=C2=A0 1 root=C2=A0 wheel=C2=A0 40960 May 10 17:20 /etc/pwd.db -rw-------=C2=A0 1 root=C2=A0 wheel=C2=A0 40960 May 10 17:20 /etc/spwd.db
/etc/master.passwd reports a null password for root, /etc/passwd
has the usual asterisk. The running system reports
root@www:/usr/src # uname -a
FreeBSD www.zefox.com 14.0-CURRENT FreeBSD 14.0-CURRENT #25 main-743516d51f:= Thu May 18 00:08:40 PDT 2023=C2=A0 =C2=A0 =C2=A0bob@www.zefox.com:/usr/obj= /usr/src/arm.armv7/sys/GENERIC arm
root@www:/usr/src # uname -KU
1400088 1400088

I've never manually run pwd_mkdb and most certainly
never set a null password for root. It looks rather
as if a null password was set for root within one
minute after running pwd_mkdb.

At this point I'm unsure how to sort out what happened.
The obvious next step is to re-establish a non-null
root password and rebuild both databases.

Is it worthwhile to check for backdoors? There's no
evidence to suggest any malicious action (and plenty
of stupidity on my end) but the tale is getting
curiouser and curiouser.

Many thanks for the quick reply!

bob prohaska




--00000000000008876b05fc9d2ed3-- From nobody Fri May 26 19:21:11 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 4QSZXF2CwZz4CpHd for ; Fri, 26 May 2023 19:21:01 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QSZXF0HWDz4MbJ; Fri, 26 May 2023 19:21:00 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Authentication-Results: mx1.freebsd.org; none Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.17.1/8.15.2) with ESMTPS id 34QJLCQY029236 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 26 May 2023 12:21:12 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.17.1/8.15.2/Submit) id 34QJLCd1029235; Fri, 26 May 2023 12:21:12 -0700 (PDT) (envelope-from fbsd) Date: Fri, 26 May 2023 12:21:11 -0700 From: bob prohaska To: Ben Laurie Cc: Mike Karels , freebsd-current@freebsd.org Subject: Re: Surprise null root password Message-ID: References: <945C9B6D-F2A8-4F0D-BDB0-49A3DE870168@karels.net> 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-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4QSZXF0HWDz4MbJ X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N 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). Any advice appreciated! bob prohaska > On Fri, 26 May 2023 at 19:45, bob prohaska wrote: > > > On Fri, May 26, 2023 at 01:03:19PM -0500, Mike Karels wrote: > > > On 26 May 2023, at 12:35, bob prohaska wrote: > > > > > > > While going through normal security email from a Pi2 > > > > running -current I was disturbed to find: > > > > > > > > Checking for passwordless accounts: > > > > root::0:0::0:0:Charlie &:/root:/bin/sh > > > > > > [details snipped] > > > /etc/master.passwd is the source, but the operational database > > > is /etc/spwd.db. You should check the date on it as well. > > > You can rebuild it with ???pwd_mkdb -p /etc/master.passwd???. > > > > At present the host reports: > > root@www:/usr/src # ls -l /etc/*p*wd* > > -rw------- 1 root wheel 2099 May 10 17:20 /etc/master.passwd > > -rw-r--r-- 1 root wheel 1831 May 10 17:20 /etc/passwd > > -rw-r--r-- 1 root wheel 40960 May 10 17:20 /etc/pwd.db > > -rw------- 1 root wheel 40960 May 10 17:20 /etc/spwd.db > > > > /etc/master.passwd reports a null password for root, /etc/passwd > > has the usual asterisk. The running system reports > > root@www:/usr/src # uname -a > > FreeBSD www.zefox.com 14.0-CURRENT FreeBSD 14.0-CURRENT #25 > > main-743516d51f: Thu May 18 00:08:40 PDT 2023 bob@www.zefox.com:/usr/obj/usr/src/arm.armv7/sys/GENERIC > > arm > > root@www:/usr/src # uname -KU > > 1400088 1400088 > > > > I've never manually run pwd_mkdb and most certainly > > never set a null password for root. It looks rather > > as if a null password was set for root within one > > minute after running pwd_mkdb. > > > > At this point I'm unsure how to sort out what happened. > > The obvious next step is to re-establish a non-null > > root password and rebuild both databases. > > > > Is it worthwhile to check for backdoors? There's no > > evidence to suggest any malicious action (and plenty > > of stupidity on my end) but the tale is getting > > curiouser and curiouser. > > > > Many thanks for the quick reply! > > > > bob prohaska > > > > > > > > > > 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? From nobody Fri May 26 23:26:06 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 4QSgz72nGlz4TPZn for ; Fri, 26 May 2023 23:26:11 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QSgz660pFz3lVL for ; Fri, 26 May 2023 23:26:10 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Authentication-Results: mx1.freebsd.org; none Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.17.1/8.15.2) with ESMTPS id 34QNQ7KG029863 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 26 May 2023 16:26:08 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.17.1/8.15.2/Submit) id 34QNQ770029862; Fri, 26 May 2023 16:26:07 -0700 (PDT) (envelope-from fbsd) Date: Fri, 26 May 2023 16:26:06 -0700 From: bob prohaska To: Yuri Cc: freebsd-current@freebsd.org Subject: Re: Surprise null root password Message-ID: References: <945C9B6D-F2A8-4F0D-BDB0-49A3DE870168@karels.net> <61e30711-f0da-2f42-3a6f-9bd91fc6b1ce@aetern.org> 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-Disposition: inline In-Reply-To: <61e30711-f0da-2f42-3a6f-9bd91fc6b1ce@aetern.org> X-Rspamd-Queue-Id: 4QSgz660pFz3lVL X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N 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 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 From nobody Sat May 27 02:28:29 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 4QSm1J2Mxjz4V5jw for ; Sat, 27 May 2023 02:28:20 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QSm1H2Ktyz42sv for ; Sat, 27 May 2023 02:28:19 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net; dmarc=none Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.17.1/8.15.2) with ESMTPS id 34R2STRl030413 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Fri, 26 May 2023 19:28:30 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.17.1/8.15.2/Submit) id 34R2STJn030412 for freebsd-current@freebsd.org; Fri, 26 May 2023 19:28:29 -0700 (PDT) (envelope-from fbsd) Date: Fri, 26 May 2023 19:28:29 -0700 From: bob prohaska To: freebsd-current@freebsd.org Subject: Re: Surprise null root password Message-ID: References: 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-Disposition: inline In-Reply-To: X-Spamd-Result: default: False [-0.52 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_SHORT(-0.98)[-0.979]; NEURAL_HAM_MEDIUM(-0.96)[-0.956]; WWW_DOT_DOMAIN(0.50)[]; MID_RHS_WWW(0.50)[]; NEURAL_HAM_LONG(-0.48)[-0.483]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; DMARC_NA(0.00)[zefox.net]; RCPT_COUNT_ONE(0.00)[1]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4QSm1H2Ktyz42sv X-Spamd-Bar: / X-ThisMailContainsUnwantedMimeParts: N It turns out all seven hosts in my cluster report a null password for root in /usr/src/etc/master.passwd: root::0:0::0:0:Charlie &:/root:/bin/sh Is that intentional? Thanks for reading, bob prohaska From nobody Sat May 27 02:52:37 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 4QSmYN16TJz4V7Y0 for ; Sat, 27 May 2023 02:52:40 +0000 (UTC) (envelope-from mike@karels.net) Received: from mail2.karels.net (mail2.karels.net [3.19.118.201]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "freebsd", Issuer "freebsd" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QSmYM5P3nz44pH for ; Sat, 27 May 2023 02:52:39 +0000 (UTC) (envelope-from mike@karels.net) Authentication-Results: mx1.freebsd.org; none Received: from mail2.karels.net (localhost [IPv6:0:0:0:0:0:0:0:1]) by mail2.karels.net (8.17.1/8.17.1) with ESMTP id 34R2qcZu071437; Fri, 26 May 2023 21:52:38 -0500 (CDT) (envelope-from mike@karels.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=karels.net; s=mail2; t=1685155958; bh=YiLVeCcLWyROWXeK61OzAGljc/e9uKQLP0v00wuWEms=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=MfknSalEPL3c89ADuFLviY8VC323gSFsClc9qCvSCFulweCFPD0FyQPP9x35w281Z xeWoAsSzNblsvvncS2RM1wNwP2j45H6NsW5OoQSB5sSekwxczsaqZpK1tCGGUGlNsQ gp05Tzxifg2EFGefnCUWQXbij8pO5bAmNAQVGg9JzLY/Vdo9MXwy9znwkoCqsXZaQq Nb8FA7DlAg54tEIZ5BlSPzsMquojEVLpU7CqFBUxWlJxFSdpb7MfiQoWQwb7BFP57W w3c/gWci19ZOevy9m1yUft0EAmNl2OnBMJYbPqtJ2zpD9NcE2b8PUjWYj45blZMGWG AVFRTSlJjpmnQ== Received: from [10.0.2.130] ([73.62.165.147]) by mail2.karels.net with ESMTPSA id puFuI3ZwcWQLFwEAs/W3XQ (envelope-from ); Fri, 26 May 2023 21:52:38 -0500 From: Mike Karels To: bob prohaska Cc: freebsd-current@freebsd.org Subject: Re: Surprise null root password Date: Fri, 26 May 2023 21:52:37 -0500 X-Mailer: MailMate (1.14r5964) Message-ID: In-Reply-To: References: 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=UTF-8 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4QSmYM5P3nz44pH X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:16509, ipnet:3.16.0.0/14, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On 26 May 2023, at 21:28, bob prohaska wrote: > It turns out all seven hosts in my cluster report > a null password for root in /usr/src/etc/master.passwd: > root::0:0::0:0:Charlie &:/root:/bin/sh > > Is that intentional? Well, it has been that way in FreeBSD since 1993, and in BSD since 1980 (4.0BSD). I guess you would say that it is intentional. The alternative would be to have a well-known password like root, but then it wouldn’t be as obvious that a local password had not been set. Mike > Thanks for reading, > > bob prohaska From nobody Sat May 27 08:31:21 2023 X-Original-To: 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 4QSw4Q3GhJz4Wk1b; Sat, 27 May 2023 08:31:34 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (vogon.madpilot.net [159.69.1.99]) (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 4QSw4P3MhGz3K69; Sat, 27 May 2023 08:31:33 +0000 (UTC) (envelope-from mad@madpilot.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=madpilot.net header.s=bjowvop61wgh header.b=NRKBmy40; spf=pass (mx1.freebsd.org: domain of mad@madpilot.net designates 159.69.1.99 as permitted sender) smtp.mailfrom=mad@madpilot.net; dmarc=pass (policy=quarantine) header.from=madpilot.net Received: from mail (mail [IPv6:fd5c:5351:d272::3]) by mail.madpilot.net (Postfix) with ESMTP id 4QSw4M6k0bz6wCQ; Sat, 27 May 2023 10:31:31 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= content-transfer-encoding:content-type:content-type:subject :subject:from:from:content-language:date:date:message-id :received; s=bjowvop61wgh; t=1685176285; x=1686990686; bh=eVQiAE ynf+ltK/0wY9/p7xfGXQpPjSv0F8m8vTR+hXU=; b=NRKBmy40m3GO+nFWxBoUuW nDWZ0CM/kllpHgncD0AU6zeh8l9ypK+fSuB26YEiYDaJ2dn4R5thkvMGAqaoZ3sg 863OvtRBO2foa/4spqPs2yStTv8pLi6jKeWXCXk1em2XruiAFLaMlKnnq1tb5Smf F3UjfRKaUvq+4uC+awFLeuAbK3ZYV0bd7syiNOWdLHR3z+C8ggIpWplYrBvig2ck Ch8HIUTOx3+TQFr+w2X0JgY/1M+FbZTn0RKHFN4x30U5bOB6eEJ89sQC/35I9yQ1 fhwhXhYRIokEWh/WZCmys8his/Z9YbczQZtU1COedqGXYGhcc7jJYZ8zbmYvjzBQ == Received: from mail.madpilot.net ([IPv6:fd5c:5351:d272::3]) by mail (mail.madpilot.net [IPv6:fd5c:5351:d272::3]) (amavisd-new, port 10026) with ESMTP id TFqCR9M1hPut; Sat, 27 May 2023 10:31:25 +0200 (CEST) Message-ID: <0edab5e7-70db-9b32-39da-54b1503ab824@madpilot.net> Date: Sat, 27 May 2023 10:31:21 +0200 To: current@FreeBSD.org, freebsd-x11@freebsd.org Content-Language: en-US From: Guido Falsi Subject: Help request: strange issue with xfce xfwm4 on AMD hardware, running head Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-1.91 / 15.00]; MISSING_MIME_VERSION(2.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.91)[-0.914]; DMARC_POLICY_ALLOW(-0.50)[madpilot.net,quarantine]; R_DKIM_ALLOW(-0.20)[madpilot.net:s=bjowvop61wgh]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; BLOCKLISTDE_FAIL(0.00)[159.69.1.99:server fail]; MLMMJ_DEST(0.00)[current@FreeBSD.org,freebsd-x11@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[madpilot.net:+]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ASN(0.00)[asn:24940, ipnet:159.69.0.0/16, country:DE]; TO_DN_NONE(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4QSw4P3MhGz3K69 X-Spamd-Bar: - X-ThisMailContainsUnwantedMimeParts: N 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 Hi, I'm seeing a strange issue with xfwm4 on my laptop running head (commit 5804b7ab378d6207130bd1685c931da6a4e76e55), using pkgbase, everything build on poudriere. I have filed an issue upstream with a description and some finding: https://gitlab.xfce.org/xfce/xfwm4/-/issues/722 I'm testing changing some things but I get the same exact error 100% repeatable. I'm now going to try older drm (machine has drm-515, will try drm-510). Don't expect a solution, but what I'm looking for is suggestions on where I could try looking for a solution. At present I'm just shuffling things around hoping to stumble on something that fixes it. I also fear this could become a more generalized problem once the cause reaches (via latest or quarterly packages, or release of 14.0 for example) more users. I'd really rather exclude this eventuality. What changed since it was running fine is base was updated to very recent head(via pkgbase) and the following ports: May 23 09:34:06 ubik pkg[4420]: xorgproto upgraded: 2022.1 -> 2022.1_1 May 23 09:34:06 ubik pkg[4420]: libxfce4menu upgraded: 4.18.3 -> 4.18.4 May 23 09:34:06 ubik pkg[4420]: double-conversion upgraded: 3.2.1 -> 3.3.0 May 23 09:34:06 ubik pkg[4420]: libuv upgraded: 1.44.2 -> 1.45.0 May 23 09:34:09 ubik pkg[4420]: FreeBSD-kernel-generic upgraded: 14.snap20230512220621 -> 14.snap20230522103000 May 23 09:34:10 ubik pkg[4420]: qt6-base reinstalled: 6.4.2_2 -> 6.4.2_2 May 23 09:34:13 ubik pkg[4420]: FreeBSD-utilities upgraded: 14.snap20230513072958 -> 14.snap20230522103000 May 23 09:34:13 ubik pkg[4420]: FreeBSD-yp upgraded: 14.snap20230425153702 -> 14.snap20230522103000 May 23 09:34:14 ubik pkg[4420]: FreeBSD-sendmail upgraded: 14.snap20230425153702 -> 14.snap20230522103000 May 23 09:34:14 ubik pkg[4420]: dua-cli upgraded: 2.19.2_2 -> 2.20.1 May 23 09:34:14 ubik pkg[4420]: FreeBSD-zoneinfo upgraded: 14.snap20230425153702 -> 14.snap20230522103000 May 23 09:34:14 ubik pkg[4420]: vmutils upgraded: 1.87.4_1 -> 1.87.6 May 23 09:34:14 ubik pkg[4420]: gexiv2 upgraded: 0.14.0 -> 0.14.1 May 23 09:34:16 ubik pkg[4420]: FreeBSD-tests upgraded: 14.snap20230512220621 -> 14.snap20230522103000 May 23 09:34:16 ubik pkg[4420]: xfce4-panel upgraded: 4.18.3_1 -> 4.18.4 May 23 09:34:19 ubik pkg[4420]: boost-libs upgraded: 1.82.0 -> 1.82.0_1 May 23 09:34:19 ubik pkg[4420]: babl upgraded: 0.1.102 -> 0.1.106 May 23 09:34:19 ubik pkg[4420]: firefox upgraded: 113.0.1,2 -> 113.0.2,2 May 23 09:34:21 ubik pkg[4420]: FreeBSD-runtime-dev upgraded: 14.snap20230512220621 -> 14.snap20230522103000 May 23 09:34:21 ubik pkg[4420]: curl upgraded: 8.0.1 -> 8.1.0 May 23 09:34:21 ubik pkg[4420]: FreeBSD-unbound upgraded: 14.snap20230512220621 -> 14.snap20230522103000 -- Guido Falsi From nobody Sat May 27 09:39:12 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 4QSxZY0xY3z4WnBZ for ; Sat, 27 May 2023 09:39:17 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QSxZY00m2z3kbD; Sat, 27 May 2023 09:39:17 +0000 (UTC) (envelope-from theraven@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685180357; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=4Ffj0IptFwffDhHJH8FA/mCxabiMdLw11KgN8LOb4Ns=; b=i5vY97ZxLBI7eAX9KiQa4mEVlG1b9duEDft64v/QVlpeO6Xm8wAIzJTgmbO+pzZCyMEenL UC5fghm83+gSTYnhNwB9XPmHzQJ86xVjCivCQrd+x6Av6KHT5IewvUjDOTZ4TJ27fqQ5SK ELYQ0nh9TelXHAWa9b/qr+Pa021yumyjePCIzUcCCleeF1R4RBlQagPAyMUm9YhiEeEeJp LDeuA2Hd1SkI9+nx1ej2ip49Lku+tp+nZpV7LDg8QqnK90Q3HlursrNR4qETisq9Yux5oR Ewa3OJHwrWwUgyRJ+qnpNr3sbFemf0cZ2g48blCwjdFm0i6OZb7qE2QrUYXlGg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685180357; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=4Ffj0IptFwffDhHJH8FA/mCxabiMdLw11KgN8LOb4Ns=; b=fl8nKN9PJMYw4lFWEbpv2DV4uPZIkdCs6EcKWtyCXk5yF5jNvqCa+P538T72CY649G4LAk RnKly6WzfQfgxQLRNB7P93Sz/OcfrHNhQmynQ+sBitJ9TESIFouIikuWRMgD0QLRJaWpTq EmdPHHNWBWwMLz2UrXPprSNM50xv2ZB3y1adssHNv9ZSXA/MWTmDtXiY5Zf10T7mQhtlS8 Yqoty/RswkC8aZJkr7cJO8anAVJaNqfmmT/GWvOwRTWp2Gbf7kb9Il0qQsh7Whh+lLsNZD 81MN3lNk+XV8mxnj53jQsFp4WJ+C+nJcF1IOgYMqpwf5x+S8AKYwGqK5vJkENw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1685180357; a=rsa-sha256; cv=none; b=uulfllS9vd9q8vbGpsoR9j0RJ8HV78WUEari2XWg89lT2ymg6E1CTsyCqJgK+vTUAa9XCA eSQWWZUDCqriT4AnPHG5Ox+xphHcClM6TdlHAuHvjiWohHUiJ377x0jI2js4UxgV/eGd6e PaTw6qpsmRO09q02qLOOpbKtKwLtPOPBVzZPdTgu+N5Hlspb51GOEAiF69WwAWkLJKPVuu 7x8G+4fxw8KriG/lyF29OSGwgPEzUzSKpmXnMkGWRmz1edAYYJqOJpuXlIIhbiMC0hWkcy 9/pwi6HkEmeT0BankxkCK6IgWAe/v9m0FgQfQUyZm6mipnjo7aqkWgFiFHifRA== Received: from smtp.theravensnest.org (smtp.theravensnest.org [45.77.103.195]) (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) (Authenticated sender: theraven) by smtp.freebsd.org (Postfix) with ESMTPSA id 4QSxZX5rvgz1Nst; Sat, 27 May 2023 09:39:16 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from smtpclient.apple (host86-136-198-116.range86-136.btcentralplus.com [86.136.198.116]) by smtp.theravensnest.org (Postfix) with ESMTPSA id AE52311851; Sat, 27 May 2023 10:39:15 +0100 (BST) Content-Type: text/plain; charset=utf-8 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 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) Subject: Re: Surprise null root password From: David Chisnall In-Reply-To: Date: Sat, 27 May 2023 10:39:12 +0100 Cc: bob prohaska , freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <850FF076-A511-4802-8D7C-2029752C3345@FreeBSD.org> References: To: Mike Karels X-Mailer: Apple Mail (2.3654.120.0.1.13) X-ThisMailContainsUnwantedMimeParts: N On 27 May 2023, at 03:52, Mike Karels wrote: >=20 > On 26 May 2023, at 21:28, bob prohaska wrote: >=20 >> It turns out all seven hosts in my cluster report >> a null password for root in /usr/src/etc/master.passwd: >> root::0:0::0:0:Charlie &:/root:/bin/sh >>=20 >> Is that intentional? >=20 > Well, it has been that way in FreeBSD since 1993, and in BSD since > 1980 (4.0BSD). I guess you would say that it is intentional. The > alternative would be to have a well-known password like root, but > then it wouldn=E2=80=99t be as obvious that a local password had not = been > set. There was a very nasty POLA violation a release or two ago. OpenSSH = defaults to disallowing empty passwords and so having a null password = was a convenient way of allowing people to su or locally log into that = user but disallowing ssh. This option does not work in recent versions = of FreeBSD. Turning on the option to permit root login while keeping = the root password blank used to be (mostly) safe because it permitted su = to root from people in the wheel group, root login via SSH key remotely = (for =E2=80=98everything is broken I can=E2=80=99t log in as a user = whose home directory is not on the root filesystem=E2=80=99 recovery) = and local login as root from consoles marked as secure. It now permits = root login from the network with a blank password. David From nobody Sat May 27 15:30:18 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 4QT5Mk0kLbz4Crpl for ; Sat, 27 May 2023 15:30:26 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QT5Mj75RZz3N48 for ; Sat, 27 May 2023 15:30:25 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685201426; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=R2Jy06IztTc1YQ1RaGvx7EAffrdSf0CsVgPE02pyuL0=; b=besCy4dGG/JujeEZC/BtCEiRdH2ZVpBjZjzvnefBMu/pNFThSnVFscGC+5IldzQOqbdZ0/ y79grC6hsPUmlFw7XDoIbLoUOiqdPSTkEL3QzUGl7r+anwzA457B/bNjA6f+hu1sC9/hqO cqNweAf8qe2L/CAJpgpJvfQiyrxfN2i1SJCnj0OJK4MdYmmBfMeG8Ws+2HXiU6u45G6aIt kRT6YO4tArwOxyM464tg6kAycfousyJXt++IIwvLNGkzEOIaPGCub0rXu0NTEsAPWvosa2 oycCk9IKfmAI7ZC4FY8fEMG970sqjEwWPFgl34woGCTaF/LI/So1+Vu5OwbpeQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685201426; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=R2Jy06IztTc1YQ1RaGvx7EAffrdSf0CsVgPE02pyuL0=; b=hJJ9NLVWBed1+Qpgipnq7q0LO7MoQx5MqWVHqQx3Xb0SPFp/SLU70VPOH6nYoxXG5UTp6N ap5gQkMRS5V4jcMsrMRuzy8/J0qUtAKYw7Y6hofhgZl9czdBsIEKSpsw3aMwW8P6g1aTYy NccoEW4TzJUectF07mv8OCQsSS2MJ6v+dZgGXYCIEpAdnDUNKwHVtuvQSFKmKs0h0mT+y/ hto0/c35dQhIv9RMQLYLYWwPHsxdP6J+6VwtpfN9FnIa9gaKnB+Ny64vuQAGUKhqr6rQP5 V6Tn2IkOgW0N3sFwKSUp2mcBglhz83wDK0LfBUntjdkquSMK5exHgI5XwGBOnA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1685201426; a=rsa-sha256; cv=none; b=o+BjwwWmvvAIAEXxPAnfSEIIr2QZrvls4t0UqylcGUDfRqZuRVZ+ztvSopy9829w6otr5n /BqyK5HM0v2ZbV1TmympDIQqHvSvaIbRai60Dad7Al15HTKuJZiF9REGGu6ZO2kjH3WYAZ /x/i8Gfh3OGLIoI2jbZ5sz4yPpdS7JSTHVOgeSfB+Izk16Z+NjF8JIsliq9Ks+YLQEJxws g3CHiFEl/NDU2/fx82nyUHKZXw7q0NETQWYaIO89MxK8UvjCtHCaT/QFQizXk+gbr4ixNK zcEARAr3uI9bToWKLkuW5Y6NOk/DYeb60OL18+Y5HBl0fU8QwA9/LS28VpzmAw== Received: from [192.168.1.10] (host-2-100-161-236.as13285.net [2.100.161.236]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: grahamperrin) by smtp.freebsd.org (Postfix) with ESMTPSA id 4QT5Mj4WNczGBt for ; Sat, 27 May 2023 15:30:25 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) Message-ID: <84482bfa-e6a4-01a6-36c3-6b6d06e3b993@freebsd.org> Date: Sat, 27 May 2023 16:30:18 +0100 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 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 To: FreeBSD CURRENT Content-Language: en-US From: Graham Perrin Subject: ZFS: panic: VERIFY3(dev->l2ad_hand <= dev->l2ad_evict) failed Organization: FreeBSD Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------YLi0l4jQipbL15RRvbYehTtV" X-ThisMailContainsUnwantedMimeParts: N This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------YLi0l4jQipbL15RRvbYehTtV Content-Type: multipart/mixed; boundary="------------LxFOOcNoT06Zs0wtnB0DNXU0"; protected-headers="v1" From: Graham Perrin To: FreeBSD CURRENT Message-ID: <84482bfa-e6a4-01a6-36c3-6b6d06e3b993@freebsd.org> Subject: ZFS: panic: VERIFY3(dev->l2ad_hand <= dev->l2ad_evict) failed --------------LxFOOcNoT06Zs0wtnB0DNXU0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 VGhyZWUgcGFuaWNzIHdpdGggYzJjOWFjODhjMmJiICgyMDIzLTA1LTI2LCAxNDAwMDg5KToN Cg0KPGh0dHBzOi8vcmV2aWV3cy5mcmVlYnNkLm9yZy9QNTY5PiBEdW1wdGltZTogMjAyMy0w NS0yNyAwMzoxNzoxNiArMDEwMA0KDQo8aHR0cHM6Ly9yZXZpZXdzLmZyZWVic2Qub3JnL1A1 NzA+IER1bXB0aW1lOiAyMDIzLTA1LTI3IDAzOjQxOjAzICswMTAwDQoNCjxodHRwczovL3Jl dmlld3MuZnJlZWJzZC5vcmcvUDU3MT4gRHVtcHRpbWU6IDIwMjMtMDUtMjcgMTQ6MDM6MzIg KzAxMDANCg0KQXJlIHRoZXkgc3ltcHRvbWF0aWMgb2YgPGh0dHBzOi8vZ2l0aHViLmNvbS9v cGVuemZzL3pmcy9pc3N1ZXMvMTM4OTk+IA0KKGZpeGVkIDIwMjMtMDUtMDkgd2l0aCANCjxo dHRwczovL2dpdGh1Yi5jb20vb3Blbnpmcy96ZnMvY29tbWl0L2QzOGM4MTVmZTI3YzAzMzU2 NGQxZjdjYzc2OWU3NGViYTExY2ZiODM+KSwgDQpvciBzaG91bGQgSSB0cmVhdCB0b2RheSdz IHBhbmljcyBhcyBzZXBhcmF0ZT8NCg0KVGhlIGZpcnN0IHBhbmljIG9jY3VycmVkIGR1cmlu ZyBpbnN0YWxsd29ybGQsIHVwdGltZSBmaXZlIG1pbnV0ZXMuDQoNClRoZSBzZWNvbmQgd2Fz IGluIHNpbmdsZSB1c2VyIG1vZGUsIHdoZW4gSSB0b29rIHRoZSB0aGlyZCBvZiB0aHJlZSBM MkFSQyANCmRldmljZXMgb25saW5lLCB1cHRpbWUgdHdlbnR5LXR3byBtaW51dGVzLg0KDQpU aGUgdGhpcmQgcGFuaWMgd2FzIHdoaWxzdCB1c2luZyBQbGFzbWEsIHdpdGhvdXQgdGhlIGRl dmljZSB0aGF0IA0KZmVhdHVyZWQgaW4gdGhlIHNlY29uZCBwYW5pYywgdXB0aW1lIHR3ZW50 eS10aHJlZSBtaW51dGVzLg0KDQpUaGUgcmVzdWx0IG9mIGEgcHJvYmUgYXQgMDc6NDkgVVRD OiANCjxodHRwczovL2JzZC1oYXJkd2FyZS5pbmZvLz9wcm9iZT02NTM3NmQ2YjQyPg0KDQo= --------------LxFOOcNoT06Zs0wtnB0DNXU0-- --------------YLi0l4jQipbL15RRvbYehTtV Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEEWT/lssMHB+28ly8Kt2dIb0oY1AsFAmRyIgoFAwAAAAAACgkQt2dIb0oY1At9 +A//dW8pDNzdcVvmCtFB1KmZyYL2sskQ1baT+g/fYf0TzyZUXsp6GwPcV0CH9M5SerEmdu389MaP 3SibgbpV4lPugQBFnLAC5qCGPsUYpeuJk/gk8xGX7hoIbq/6RRQxkNKKafv7JW4G0bAWKOP+PWWn Rc2/fmS/NaVhTiP3A6F0wHiRekVVYxDHTGLAXdyVKwccEyl9qeOdgxG0yiU4oVs8csoDSDVdJr/I eY2AaSWD/9pf2mQjnfgGAnF87qeEzYMuGwPReMtUI9MKRQxt9gr4Og6aqZPK1Hv2qQRfQXAWGoAI r1YH2ves8Mb3uME9Pd1CUH7Y1AYSX+gJmecWMvpe41rvsnIYTElthVY4jJBJVaQyJXtbCdYQue+g BQJeEUf+B8V8SlrD8A43oTDdB3uiV4cW/IvSu8vdgSsrugS86H2atmY4zJYKfN3Hk9GtjTRNdo5A zSMlRjoSB43Drf6zuBWNSahenHYm9LmTEE8asHFh9qC0Onycyexc2HN1MT86XvTKJeX63RxYH2oV kDaCBd0SNI8hZ5k40QuQk8VfwoDoLkc9LWiEiXicDEq+3orskwmYUyQNLxaESLstWn5LgkOZSoRt clEB24ho7J9/UHTrZiix9zpK66Y+kBINaeMhfiQk1eIIJMi2Z9tNOAC7Bc9OnSQLsy1qIEkHMBoa fHg= =alBq -----END PGP SIGNATURE----- --------------YLi0l4jQipbL15RRvbYehTtV-- From nobody Sat May 27 17:22:38 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 4QT7sN0FJ1z4V4M9 for ; Sat, 27 May 2023 17:22:48 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4QT7sM3Yynz3vN1 for ; Sat, 27 May 2023 17:22:47 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Authentication-Results: mx1.freebsd.org; none Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id 34RHMcJ2025610; Sat, 27 May 2023 10:22:38 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id 34RHMcRG025609; Sat, 27 May 2023 10:22:38 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <202305271722.34RHMcRG025609@gndrsh.dnsmgr.net> Subject: Re: Surprise null root password In-Reply-To: <945C9B6D-F2A8-4F0D-BDB0-49A3DE870168@karels.net> To: Mike Karels Date: Sat, 27 May 2023 10:22:38 -0700 (PDT) CC: bob prohaska , freebsd-current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] 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-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 4QT7sM3Yynz3vN1 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N > On 26 May 2023, at 12:35, bob prohaska wrote: > > > While going through normal security email from a Pi2 > > running -current I was disturbed to find: > > > > Checking for passwordless accounts: > > root::0:0::0:0:Charlie &:/root:/bin/sh > > > > The machine had locked up on a -j4 buildworld since > > sending the mail, so it was taken off the net, power > > cycled and started single-user. > > > > Sure enough, /etc/master.passwd contained a > > null password for root, but the last modification > > to the file was two weeks ago according to ls -l. > > > > Stranger still, when fsck'd and brought up multi-user, > > the normal password was still honored and a null > > password rejected for both regular and root account. > > > > AFAIK, /etc/master.passwd is _the_ password repository, > > but clearly I'm wrong. > > /etc/master.passwd is the source, but the operational database > is /etc/spwd.db. You should check the date on it as well. > You can rebuild it with ?pwd_mkdb -p /etc/master.passwd?. BUT if infact /etc/master.passwd has been clobbered, BUT /etc/spwd.db still contains the correct data you would not want to do the above, as that would put the null passwd for root into /etc/*pwd.db, and/or possible other accounts. I do not know of a utility that can dump /etc/*pwd.db and recreate a master.passwd file, anyone? > Mike > > > If somebody can tell me what's going on and what to > > check for before placing the machine back on line > > it would be much appreciated. > > > > Thanks for reading, > > > > bob prohaska > > -- Rod Grimes rgrimes@freebsd.org From nobody Sat May 27 17:36:18 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 4QT8913VhGz4V4jX for ; Sat, 27 May 2023 17:36:21 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4QT8910b0Wz3wlv for ; Sat, 27 May 2023 17:36:20 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Authentication-Results: mx1.freebsd.org; none Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id 34RHaIZH025654; Sat, 27 May 2023 10:36:18 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id 34RHaI1H025653; Sat, 27 May 2023 10:36:18 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <202305271736.34RHaI1H025653@gndrsh.dnsmgr.net> Subject: Re: Surprise null root password In-Reply-To: To: bob prohaska Date: Sat, 27 May 2023 10:36:18 -0700 (PDT) CC: freebsd-current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] 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-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 4QT8910b0Wz3wlv X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N > It turns out all seven hosts in my cluster report > a null password for root in /usr/src/etc/master.passwd: > root::0:0::0:0:Charlie &:/root:/bin/sh > > Is that intentional? No, but I suspect your build/update procedures are infact telling the system to do this. Someone else pointed out etcupdate, which iirc you are using, with the update of "thiers all" infact would overwrite /etc/master.passwd. I do not know that etcupdate has the smarts to know that if it overwrites /etc/master.passwd it needs to run a pwd_mkdb -p /etc/master.passwd. etcupdate infact does have the smarts to run a pwd_mkdb. Hum, it also has some special casing of PREWORLD_FILES, which is /etc/master.passwd and etc/group. Perhaps something in that process went wrong. -- Rod Grimes rgrimes@freebsd.org From nobody Sat May 27 18:03:51 2023 X-Original-To: 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 4QT8nP75jlz4V6d2; Sat, 27 May 2023 18:04:25 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (vogon.madpilot.net [159.69.1.99]) (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 4QT8nP2M67z420s; Sat, 27 May 2023 18:04:25 +0000 (UTC) (envelope-from mad@madpilot.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=madpilot.net header.s=bjowvop61wgh header.b="D 3jdsam"; spf=pass (mx1.freebsd.org: domain of mad@madpilot.net designates 159.69.1.99 as permitted sender) smtp.mailfrom=mad@madpilot.net; dmarc=pass (policy=quarantine) header.from=madpilot.net Received: from mail (mail [IPv6:fd5c:5351:d272::3]) by mail.madpilot.net (Postfix) with ESMTP id 4QT8mp1Nj7z6yqv; Sat, 27 May 2023 20:03:54 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= content-transfer-encoding:content-type:content-type:in-reply-to :references:from:from:content-language:subject:subject:date:date :message-id:received; s=bjowvop61wgh; t=1685210629; x= 1687025030; bh=+vK2BRnXwEav3ch6EBTpo/q7u+USrrqmSRK4a3c7L/k=; b=D 3jdsamiMB0wGtLpGEozvcHJKtLv0iqeYDwdVnXDFovUMFC2Lx4EcR8qwgAWQLI4+ ugKmHxlzW7VCrxTURlkMNVvq5NjjCTxL5WUFbugT5DQFEqDVcn3DMl4uP1/Akoef 6soXc9eEipz0E+orIlRv8ChIHUoO53kZsbMp8xHpf8KaX32DA0lerRBOUQ2S4lHl LjtdQJbGtauz6o/FUAn91CEIWm+7Nh7oM4UOpnEBHS725uxnHYMLpVHH0Ft6135F hzJDS4NUrqxjb3zuJyr2bXwIJSJ8eGvSsf/JdCNC3xXBzrxfmOp4OFIbJYtLiSBy a+LuQbhMSxnggwe4yXzLQ== Received: from mail.madpilot.net ([IPv6:fd5c:5351:d272::3]) by mail (mail.madpilot.net [IPv6:fd5c:5351:d272::3]) (amavisd-new, port 10026) with ESMTP id AquHq5k-_qj0; Sat, 27 May 2023 20:03:49 +0200 (CEST) Message-ID: <2931778c-9d23-90b8-719f-e34cfa41f188@madpilot.net> Date: Sat, 27 May 2023 20:03:51 +0200 Subject: Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head Content-Language: en-US From: Guido Falsi To: current@FreeBSD.org, freebsd-x11@freebsd.org References: <0edab5e7-70db-9b32-39da-54b1503ab824@madpilot.net> In-Reply-To: <0edab5e7-70db-9b32-39da-54b1503ab824@madpilot.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-1.99 / 15.00]; MISSING_MIME_VERSION(2.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.988]; DMARC_POLICY_ALLOW(-0.50)[madpilot.net,quarantine]; R_DKIM_ALLOW(-0.20)[madpilot.net:s=bjowvop61wgh]; R_SPF_ALLOW(-0.20)[+mx:c]; MIME_GOOD(-0.10)[text/plain]; BLOCKLISTDE_FAIL(0.00)[159.69.1.99:server fail]; MLMMJ_DEST(0.00)[current@FreeBSD.org,freebsd-x11@freebsd.org]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[madpilot.net:+]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; TO_DN_NONE(0.00)[]; ASN(0.00)[asn:24940, ipnet:159.69.0.0/16, country:DE]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4QT8nP2M67z420s X-Spamd-Bar: - X-ThisMailContainsUnwantedMimeParts: N 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 On 27/05/23 10:31, Guido Falsi wrote: > Hi, > > I'm seeing a strange issue with xfwm4 on my laptop running head (commit > 5804b7ab378d6207130bd1685c931da6a4e76e55), using pkgbase, everything > build on poudriere. > > I have filed an issue upstream with a description and some finding: > > https://gitlab.xfce.org/xfce/xfwm4/-/issues/722 > > I'm testing changing some things but I get the same exact error 100% > repeatable. > A friend of mine suggested trying to disable DRI 3 and this indeed allowed xfwm4 to not crash. This is a workaround, not a fix, and does not explain what is causing the behavior. Not sure where I should be looking, I'll also check changes in kernel that could be related. Again if anyone has some insight please share! -- Guido Falsi From nobody Sat May 27 22:42:11 2023 X-Original-To: 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 4QTGy91HJKz4WsjC; Sat, 27 May 2023 22:42:25 +0000 (UTC) (envelope-from agh@riseup.net) Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx1.riseup.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QTGy86LVyz3DtF; Sat, 27 May 2023 22:42:24 +0000 (UTC) (envelope-from agh@riseup.net) Authentication-Results: mx1.freebsd.org; none Received: from fews01-sea.riseup.net (fews01-sea-pn.riseup.net [10.0.1.109]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx1.riseup.net (Postfix) with ESMTPS id 4QTGy70QWKzDq8b; Sat, 27 May 2023 22:42:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1685227343; bh=LM/l6fDvjXwvZRaSVElv2ULDBi8frQQeOFUbLmB31BU=; h=Date:From:To:Subject:In-Reply-To:References:From; b=QnkBx+peCH/MbwOSKF3V7XClTF+w1z27F4LrQOC1ume6k3od0kIZKsxQnVjnwFAHt 6wTRNXSbIuhuC3QamFvpOoaZQdoYQwRqHSfgYz0cf5e8lKcCHuMSWSbhqgdHveq7CB y2KqtxRAsByeTe47FqKpAYwQHdCS7bp2vN/5o5Jc= X-Riseup-User-ID: E9BC899ADFD38CDD952B76B7813DFA89DEA5239C87B1AF75B4339F8F76457F02 Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews01-sea.riseup.net (Postfix) with ESMTPSA id 4QTGy55XJdzJn8G; Sat, 27 May 2023 22:42:21 +0000 (UTC) Date: Sun, 28 May 2023 06:42:11 +0800 From: Alastair Hogge To: freebsd-current@freebsd.org, Guido Falsi , current@FreeBSD.org, freebsd-x11@freebsd.org Subject: =?US-ASCII?Q?Re=3A_Help_request=3A_strange_issue_with_x?= =?US-ASCII?Q?fce_xfwm4_on_AMD_hardware=2C_running_head?= In-Reply-To: <2931778c-9d23-90b8-719f-e34cfa41f188@madpilot.net> References: <0edab5e7-70db-9b32-39da-54b1503ab824@madpilot.net> <2931778c-9d23-90b8-719f-e34cfa41f188@madpilot.net> Message-ID: <226125B8-01E1-44B2-956B-A3CCECF56F7A@riseup.net> 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: multipart/alternative; boundary=----WMS9OG0AY97JNV22UULNHOBHPMZSF0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4QTGy86LVyz3DtF X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:16652, ipnet:198.252.153.0/24, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N ------WMS9OG0AY97JNV22UULNHOBHPMZSF0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello, Is there some way to test your X session with minimum components, and slow= ly adding whatever XFCE does? I would switch from using a X Display Manager, and launch X from the login= vty using startx (if not already ), with a minimum =2Exinitrc=2E I would f= ind out what is needed to get a minimal XFCE going, for example, maybe just= the Window Manager, no Compositor, or nothing at all to see if X handles t= he display mode setting at all=2E Also, where are your X logs? It is is normally at /var/log/X=2Esomething= =2E It this log empty after the crash? To anarchy and health=20 On 28 May 2023 2:03:51 am AWST, Guido Falsi wrote: >On 27/05/23 10:31, Guido Falsi wrote: >> Hi, >>=20 >> I'm seeing a strange issue with xfwm4 on my laptop running head (commit= 5804b7ab378d6207130bd1685c931da6a4e76e55), using pkgbase, everything build= on poudriere=2E >>=20 >> I have filed an issue upstream with a description and some finding: >>=20 >> https://gitlab=2Exfce=2Eorg/xfce/xfwm4/-/issues/722 >>=20 >> I'm testing changing some things but I get the same exact error 100% re= peatable=2E >>=20 > >A friend of mine suggested trying to disable DRI 3 and this indeed allowe= d xfwm4 to not crash=2E > >This is a workaround, not a fix, and does not explain what is causing the= behavior=2E > >Not sure where I should be looking, I'll also check changes in kernel tha= t could be related=2E > >Again if anyone has some insight please share! > >--=20 >Guido Falsi > > --=20 Sent from a device with a tiny bloody screen and no hard keyboard; please = excuse my brevity=2E ------WMS9OG0AY97JNV22UULNHOBHPMZSF0 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hello,

Is there some way = to test your X session with minimum components, and slowly adding whatever = XFCE does?

I would switch from using a X Display Manager, and launch= X from the login vty using startx (if not already ), with a minimum =2Exin= itrc=2E I would find out what is needed to get a minimal XFCE going, for ex= ample, maybe just the Window Manager, no Compositor, or nothing at all to s= ee if X handles the display mode setting at all=2E

Also, where are y= our X logs? It is is normally at /var/log/X=2Esomething=2E It this log empt= y after the crash?


To anarchy and health


On 28 May 2023 2:03:51 am AWST, Guido F= alsi <mad@madpilot=2Enet> wrote:
On 27/05/23 10:31, Guido Falsi wro=
te:
Hi,

I'm seeing a strange issue with xfwm4 on my laptop running =
head (commit 5804b7ab378d6207130bd1685c931da6a4e76e55), using pkgbase, ever=
ything build on poudriere=2E

I have filed an issue upstream with a d=
escription and some finding:

https://gitlab=2Exfce=2Eorg/xfce/xfwm4/-/issues/72=
2

I'm testing changing some things but I get the same exact erro=
r 100% repeatable=2E


A frie=
nd of mine suggested trying to disable DRI 3 and this indeed allowed xfwm4 =
to not crash=2E

This is a workaround, not a fix, and does not explai=
n what is causing the behavior=2E

Not sure where I should be looking=
, I'll also check changes in kernel that could be related=2E

Again i=
f anyone has some insight please share!

--
Sent from a dev= ice with a tiny bloody screen and no hard keyboard; please excuse my brevit= y=2E
------WMS9OG0AY97JNV22UULNHOBHPMZSF0-- From nobody Sat May 27 22:42:11 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 4QTGy91HJKz4WsjC; Sat, 27 May 2023 22:42:25 +0000 (UTC) (envelope-from agh@riseup.net) Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx1.riseup.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QTGy86LVyz3DtF; Sat, 27 May 2023 22:42:24 +0000 (UTC) (envelope-from agh@riseup.net) Authentication-Results: mx1.freebsd.org; none Received: from fews01-sea.riseup.net (fews01-sea-pn.riseup.net [10.0.1.109]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx1.riseup.net (Postfix) with ESMTPS id 4QTGy70QWKzDq8b; Sat, 27 May 2023 22:42:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1685227343; bh=LM/l6fDvjXwvZRaSVElv2ULDBi8frQQeOFUbLmB31BU=; h=Date:From:To:Subject:In-Reply-To:References:From; b=QnkBx+peCH/MbwOSKF3V7XClTF+w1z27F4LrQOC1ume6k3od0kIZKsxQnVjnwFAHt 6wTRNXSbIuhuC3QamFvpOoaZQdoYQwRqHSfgYz0cf5e8lKcCHuMSWSbhqgdHveq7CB y2KqtxRAsByeTe47FqKpAYwQHdCS7bp2vN/5o5Jc= X-Riseup-User-ID: E9BC899ADFD38CDD952B76B7813DFA89DEA5239C87B1AF75B4339F8F76457F02 Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews01-sea.riseup.net (Postfix) with ESMTPSA id 4QTGy55XJdzJn8G; Sat, 27 May 2023 22:42:21 +0000 (UTC) Date: Sun, 28 May 2023 06:42:11 +0800 From: Alastair Hogge To: freebsd-current@freebsd.org, Guido Falsi , current@FreeBSD.org, freebsd-x11@freebsd.org Subject: =?US-ASCII?Q?Re=3A_Help_request=3A_strange_issue_with_x?= =?US-ASCII?Q?fce_xfwm4_on_AMD_hardware=2C_running_head?= In-Reply-To: <2931778c-9d23-90b8-719f-e34cfa41f188@madpilot.net> References: <0edab5e7-70db-9b32-39da-54b1503ab824@madpilot.net> <2931778c-9d23-90b8-719f-e34cfa41f188@madpilot.net> Message-ID: <226125B8-01E1-44B2-956B-A3CCECF56F7A@riseup.net> 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: multipart/alternative; boundary=----WMS9OG0AY97JNV22UULNHOBHPMZSF0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4QTGy86LVyz3DtF X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:16652, ipnet:198.252.153.0/24, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N ------WMS9OG0AY97JNV22UULNHOBHPMZSF0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello, Is there some way to test your X session with minimum components, and slow= ly adding whatever XFCE does? I would switch from using a X Display Manager, and launch X from the login= vty using startx (if not already ), with a minimum =2Exinitrc=2E I would f= ind out what is needed to get a minimal XFCE going, for example, maybe just= the Window Manager, no Compositor, or nothing at all to see if X handles t= he display mode setting at all=2E Also, where are your X logs? It is is normally at /var/log/X=2Esomething= =2E It this log empty after the crash? To anarchy and health=20 On 28 May 2023 2:03:51 am AWST, Guido Falsi wrote: >On 27/05/23 10:31, Guido Falsi wrote: >> Hi, >>=20 >> I'm seeing a strange issue with xfwm4 on my laptop running head (commit= 5804b7ab378d6207130bd1685c931da6a4e76e55), using pkgbase, everything build= on poudriere=2E >>=20 >> I have filed an issue upstream with a description and some finding: >>=20 >> https://gitlab=2Exfce=2Eorg/xfce/xfwm4/-/issues/722 >>=20 >> I'm testing changing some things but I get the same exact error 100% re= peatable=2E >>=20 > >A friend of mine suggested trying to disable DRI 3 and this indeed allowe= d xfwm4 to not crash=2E > >This is a workaround, not a fix, and does not explain what is causing the= behavior=2E > >Not sure where I should be looking, I'll also check changes in kernel tha= t could be related=2E > >Again if anyone has some insight please share! > >--=20 >Guido Falsi > > --=20 Sent from a device with a tiny bloody screen and no hard keyboard; please = excuse my brevity=2E ------WMS9OG0AY97JNV22UULNHOBHPMZSF0 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hello,

Is there some way = to test your X session with minimum components, and slowly adding whatever = XFCE does?

I would switch from using a X Display Manager, and launch= X from the login vty using startx (if not already ), with a minimum =2Exin= itrc=2E I would find out what is needed to get a minimal XFCE going, for ex= ample, maybe just the Window Manager, no Compositor, or nothing at all to s= ee if X handles the display mode setting at all=2E

Also, where are y= our X logs? It is is normally at /var/log/X=2Esomething=2E It this log empt= y after the crash?


To anarchy and health


On 28 May 2023 2:03:51 am AWST, Guido F= alsi <mad@madpilot=2Enet> wrote:
On 27/05/23 10:31, Guido Falsi wro=
te:
Hi,

I'm seeing a strange issue with xfwm4 on my laptop running =
head (commit 5804b7ab378d6207130bd1685c931da6a4e76e55), using pkgbase, ever=
ything build on poudriere=2E

I have filed an issue upstream with a d=
escription and some finding:

https://gitlab=2Exfce=2Eorg/xfce/xfwm4/-/issues/72=
2

I'm testing changing some things but I get the same exact erro=
r 100% repeatable=2E


A frie=
nd of mine suggested trying to disable DRI 3 and this indeed allowed xfwm4 =
to not crash=2E

This is a workaround, not a fix, and does not explai=
n what is causing the behavior=2E

Not sure where I should be looking=
, I'll also check changes in kernel that could be related=2E

Again i=
f anyone has some insight please share!

--
Sent from a dev= ice with a tiny bloody screen and no hard keyboard; please excuse my brevit= y=2E
------WMS9OG0AY97JNV22UULNHOBHPMZSF0--