From nobody Sat Feb 18 23:06:20 2023 X-Original-To: freebsd-arm@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 4PK4764zK3z3s2DT for ; Sat, 18 Feb 2023 23:06:26 +0000 (UTC) (envelope-from void@f-m.fm) 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 4PK4751vC6z3rB2 for ; Sat, 18 Feb 2023 23:06:25 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm1 header.b="N9o/iB8O"; dkim=pass header.d=messagingengine.com header.s=fm1 header.b=MAPPrbl3; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 64.147.123.25 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id C90BF3200564 for ; Sat, 18 Feb 2023 18:06:23 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Sat, 18 Feb 2023 18:06:23 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :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=1676761583; x=1676847983; bh=5ajuCaDD5h 0D8VCsNcy9SufMit3fueFXYhID+skDWdM=; b=N9o/iB8OX9cNFmGFSfhmwTEvtd X/rm8rRV6svf+FWL0rsfobi02rWcc/MzLbx0Ph7+8l/xemnQEbuFzJPTatoJ6scV Y0aLECEH2FRmkUPu8HRJLh4cROhzDb6Osk0QB4NQetkmi1sveGRN7JdWJ7zsUYg1 6T7kWgMtqjyiHz8kG6zZZql76GcWFVrHcEw/Bn9y391gQXH2995qWisAPusB/eYQ 1GKqP89pNy7EK0nRs55vRD4QJwfT1FdGgJP5ZC0V0FQQEnMpxOxPBAOX9KcHup+Y d+1Z4Z45I5irLz+O/k2lfib4mcMr+Hu1VjAe0FQljc2rmdy5c13EVTDZNVPQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=1676761583; x=1676847983; bh=5ajuCaDD5h0D8VCsNcy9SufMit3f ueFXYhID+skDWdM=; b=MAPPrbl3JISwLMvGlh5YgnVt13gSIKs7RBIWvg6HSCGe LkN7fdkbEZQESaLWkEY5hJ7WtzzsToMHoMuRxo0jeskdwoHjtnbqWKvU4bZARJIK QVI23sTjW+D25Y8dTOh2W8XYsTmx+FSYZNlNtxWtZrJOosaWhz4luSqKf+XXN8ua 7mtWh7e/uzQtBGj8dPD/k8ivhuXILKOM5RPLF9qdnAg1y4VJ+g1rejxzKTw56BaN Sa1svHkbWBfhllf7xJRJ+/leZ21zOK5U7Jnr8l+2EBIPykItRVlpb5dwgMTPJHMJ ViNmaAXMdhOb4tgJQFrDBnTnmYQLa6AIZR3VIpwt7g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudejvddgtdegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujgesthdtre dttddtvdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggftrfgr thhtvghrnheptdfhheeuteejudffkefhtdfhfeekgedtvdeiteevgfejtdfgfeffhfeuie eltdeinecuffhomhgrihhnpehfrhgvvggsshgurdhorhhgnecuvehluhhsthgvrhfuihii vgeptdenucfrrghrrghmpehmrghilhhfrhhomhepvhhoihgusehfqdhmrdhfmh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Sat, 18 Feb 2023 18:06:22 -0500 (EST) Date: Sat, 18 Feb 2023 23:06:20 +0000 From: void To: freebsd-arm@freebsd.org Subject: Re: freebsd-update confusion Message-ID: Mail-Followup-To: freebsd-arm@freebsd.org References: List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: X-Spamd-Result: default: False [-4.58 / 15.00]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.98)[-0.977]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm1,messagingengine.com:s=fm1]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.25]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.25:from]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; RCPT_COUNT_ONE(0.00)[1]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; FREEMAIL_FROM(0.00)[f-m.fm]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US]; FROM_HAS_DN(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[64.147.123.25:from]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4PK4751vC6z3rB2 X-Spamd-Bar: ---- X-ThisMailContainsUnwantedMimeParts: N Hello Herbert, On Sat, Feb 18, 2023 at 11:11:50PM +0100, Herbert J. Skuhra wrote: >On Sat, Feb 18, 2023 at 09:53:56PM +0000, void wrote: >> In https://lists.freebsd.org/archives/freebsd-security/2023-February/000146.html >> there's an SA for openssl. >> >> If I upgrade (buildworld etc) on an amd box, it gets: >> >> % openssl version >> OpenSSL 1.1.1t-freebsd 7 Feb 2023 >> >> (as expected) > >This is either stable/13, releng/13.2 or main where openssl was updated >to version OpenSSL 1.1.1t. > >> If freebsd-update is run on a 13.1-R arm64 machine, installed updates then >> rebooted, it gets: >> >> $ openssl version >> OpenSSL 1.1.1o-freebsd 3 May 2022 >> >> ??? >> >> The freebsd-update was run about 10 mins ago (feb 18th 1821 UTC) > >This is releng/13.1 where openssl is still OpenSSL 1.1.1o; only security >fixes were applied. This is the bit that was confusing me. I thought 1.1.1t was with the security fixes. >You will get OpenSSL 1.1.1t after upgrading to >13.2-RELEASE (expected to be released next month). https://lists.freebsd.org/archives/freebsd-security/2023-February/000146.html has this: Corrected: 2023-02-07 22:38:40 UTC (stable/13, 13.1-STABLE) 2023-02-16 17:58:13 UTC (releng/13.1, 13.1-RELEASE-p7) 2023-02-07 23:09:41 UTC (stable/12, 12.4-STABLE) 2023-02-16 18:04:12 UTC (releng/12.4, 12.4-RELEASE-p2) 2023-02-16 18:03:37 UTC (releng/12.3, 12.3-RELEASE-p12) So, if I'm understanding you correctly, none of those releases indicated above would go to 1.1.1t ? >What's the output of 'freebsd-version -kru'? It will tell you if your >system is up-to-date. % freebsd-version -kru 13.1-RELEASE-p6 13.1-RELEASE-p6 13.1-RELEASE-p7 It's really kind of opaque (to me) that openssl version is '1.1.1o-freebsd 3 May 2022' *after* the update has been applied. If it was something like '1.1.1o-freebsd-p1 16 Feb 2023', I'd feel a bit better, because as it stands, it looks like, on the face of it, that openssl hasn't been patched. Otherwise wouldn't the versioning info change in some respect, to indicate that it had? --