From nobody Wed Nov 2 15:27:23 2022 X-Original-To: freebsd-questions@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 4N2W4144NZz4g9j6 for ; Wed, 2 Nov 2022 15:28:01 +0000 (UTC) (envelope-from kudzu@tenebras.com) Received: from mail-yb1-xb2b.google.com (mail-yb1-xb2b.google.com [IPv6:2607:f8b0:4864:20::b2b]) (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 4N2W40458rz3Xxm for ; Wed, 2 Nov 2022 15:28:00 +0000 (UTC) (envelope-from kudzu@tenebras.com) Received: by mail-yb1-xb2b.google.com with SMTP id 129so2217848ybb.12 for ; Wed, 02 Nov 2022 08:28:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tenebras-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=kU6ROsFDy5SdSuXj/KeHz3jEdeGXeeT7RqzEGOHbWmk=; b=tAVVEOLez0KueONsP+GDAZG0FIVN3kx/haF5VJaGlSO1l5kbDrX4N7qesQTtqFvyaK Odl661kM8vEKX0b3nljIlQTxq3TD9KdYG2n4rcoePXrILS6vCyHOEGeCDBxEeNguiecq ywIg1OsGXtBLisgnrrq6oA5dxmhLJXgTt+/4dJ2JstAyoz6iHwndNXXfhS8r1SJs9jPK 7m0QxvpAXo8g5HC0jqEtxbKJ98o7X1PARNzQd+MjUiGL5yhY1yyPjPFHId79cBRP21P/ vkgmOSEQYlheEPOXoFbAScdvSPXOgymI/cCGXm0OHh9q60gl4Eb0OVivgsIdPlSr0uev XMXw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=kU6ROsFDy5SdSuXj/KeHz3jEdeGXeeT7RqzEGOHbWmk=; b=F5dL3iG+WRYamq0O1i3OnoE9U1bU38ZwQqhKyv1BRZAcmSmd1d5SP1lg8g4A36u1+Q Ogg4vAsUQCoMjfsBNkVO5dZkDrZMHme4txz8Rwiwg74uqYDqE6Sa9f+0FEURvU9VHtPF yIH5W+Jb2dwcTeFiAc2ZXDn/39ElXZhVKkTJNQ1RJhCjg319BS6fVYgOFIgf3gwLkJdK U2Zn+k/BbyYShbCJsluk+wK61TtsQCUBYvGTLXNdllY4L/dv+U4hiDVQC4H8LO2q6lM5 bZnEbE0Z51AFvmNp00lAgc75eXnEgs5cRkSS1JryDos6D0OICaYq2PA3BlT9iLsrV/52 xlyg== X-Gm-Message-State: ACrzQf2a3A2KBEAzHAqPPK/7NP25OWgs+yBWYuhoKdtyKOe8pQSli8X1 CW8mKh/MhFWOwPnS6mxQuBoHPJrqpjU9GMG27A3cAg== X-Google-Smtp-Source: AMsMyM5h0ZdZYki+XHj/mfUrQzrKHaR2l0OGpWUrTAmDSrW18KshqngWHYJqAtikOiHWBXjfIa2dz4fp3cjwTsA3bX0= X-Received: by 2002:a25:df10:0:b0:6cf:f148:7cdb with SMTP id w16-20020a25df10000000b006cff1487cdbmr2912102ybg.80.1667402879517; Wed, 02 Nov 2022 08:27:59 -0700 (PDT) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Michael Sierchio Date: Wed, 2 Nov 2022 11:27:23 -0400 Message-ID: Subject: Re: 12.3 EOL warning? To: Kyle Evans Cc: Arthur Chance , FreeBSD-Questions , FreeBSD Security Team Content-Type: multipart/alternative; boundary="00000000000054e2a105ec7e7c5a" X-Rspamd-Queue-Id: 4N2W40458rz3Xxm X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=tenebras-com.20210112.gappssmtp.com header.s=20210112 header.b=tAVVEOLe; dmarc=none; spf=none (mx1.freebsd.org: domain of kudzu@tenebras.com has no SPF policy when checking 2607:f8b0:4864:20::b2b) smtp.mailfrom=kudzu@tenebras.com X-Spamd-Result: default: False [-2.30 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[tenebras-com.20210112.gappssmtp.com:s=20210112]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::b2b:from]; MLMMJ_DEST(0.00)[freebsd-questions@freebsd.org]; R_SPF_NA(0.00)[no SPF record]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[tenebras-com.20210112.gappssmtp.com:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; TO_DN_ALL(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; DMARC_NA(0.00)[tenebras.com]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N --00000000000054e2a105ec7e7c5a Content-Type: text/plain; charset="UTF-8" On Wed, Nov 2, 2022 at 11:22 AM Kyle Evans wrote: > On Wed, Nov 2, 2022 at 3:15 AM Arthur Chance wrote: > > > > Patching a 12.3 system to deal with the latest security advisory I got > > > > WARNING: FreeBSD 12.3-RELEASE-p6 is approaching its End-of-Life date. > > It is strongly recommended that you upgrade to a newer > > release within the next 2 months. > > > freebsd-update metadata includes the EoL date, which we don't > typically know when a release is cut since it depends on an > undetermined schedule for the next release. I asked secteam@ a while > back if we could just specify the end of branch as the EoL for new > releases until re@ confirms a schedule to tune that back with (which > makes sense, since it *will* be the end of the branch if all of re@ > decides that a nice prolonged beach vacation sounds more fun). I don't > know that that went anywhere, but we really need to do something to > avoid this kind of question coming up because we get it wrong more > often than not. CC secteam@. > Updating to 12.3-RELEASE-p7 quiets the warning. --00000000000054e2a105ec7e7c5a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Wed, Nov 2, 2022 at 11:22 AM Kyle = Evans <kevans@freebsd.org> = wrote:
On Wed, N= ov 2, 2022 at 3:15 AM Arthur Chance <freebsd@qeng-ho.org> wrote:
>
> Patching a 12.3 system to deal with the latest security advisory I got=
>
> WARNING: FreeBSD 12.3-RELEASE-p6 is approaching its End-of-Life date.<= br> > It is strongly recommended that you upgrade to a newer
> release within the next 2 months.


freebsd-update metadata includes the EoL date, which we don't
typically know when a release is cut since it depends on an
undetermined schedule for the next release. I asked secteam@ a while
back if we could just specify the end of branch as the EoL for new
releases until re@ confirms a schedule to tune that back with (which
makes sense, since it *will* be the end of the branch if all of re@
decides that a nice prolonged beach vacation sounds more fun). I don't<= br> know that that went anywhere, but we really need to do something to
avoid this kind of question coming up because we get it wrong more
often than not. CC secteam@.

Updating t= o 12.3-RELEASE-p7 quiets the warning.
=C2=A0
--00000000000054e2a105ec7e7c5a--