From nobody Sat Oct 01 00:05:53 2022 X-Original-To: ports-bugs@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 4MfS6q07bRz4dhV9 for ; Sat, 1 Oct 2022 00:05:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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 "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4MfS6p66HGz3qjx for ; Sat, 1 Oct 2022 00:05:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4MfS6p4mgXzLL5 for ; Sat, 1 Oct 2022 00:05:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 29105ssB020342 for ; Sat, 1 Oct 2022 00:05:54 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 29105sYP020341 for ports-bugs@FreeBSD.org; Sat, 1 Oct 2022 00:05:54 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 264232] www/mattermost-{server,webapp}: Update to 7.3.0 Date: Sat, 01 Oct 2022 00:05:53 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: needs-patch, needs-qa, security X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: ports-bugs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: cc keywords priority Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Ports bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-ports-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports-bugs@freebsd.org X-BeenThere: freebsd-ports-bugs@freebsd.org MIME-Version: 1.0 ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1664582754; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=iEWcuJTQC98H3KfDvDYAJb1DXEJS6BBXc3Jez5y2NF0=; b=yUIcqIISna2GFPTiXQEjCclENFqHWulG18gC53UoEiy1afFzR6uIs6XDSm0cLACcc9XxHw nsmLuGpT0xDVKhnqdhDYtOkq2YoxnIzt44Opf7WsSkLLrv7/vln7sm9L/vStjTiIsncoFt jiC59F14UXAOeksYda3hdJb+KGP6Lrbp46aTpcyPkbiQhjfkOboFVAjuQF5gDXK1WFhiBp LFcZixJA/5h24VRZYmvJCHJAv3M+Wh7trhg3XPyu/+f5y9uZLQzL6M6eGZpOBZs/rkaJAz Gy3N04cvleLnc/QwV63G3QTAQkWkAcv85Qp1t7M8hEDWOMjAepDSU9m7gP8VPg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1664582754; a=rsa-sha256; cv=none; b=HE7uzPDbmWx+tNh7ldXZoNOASD4HKfMI7Otul+jUbQdicnSlwC5NQL6Xhe7kVUnleNoFAS 4JrxvLTgeGuDbTyUErQ00JHko/MHsLUlYfD7gKvQoTFfilddlFjb+6Kx9V3lBKPsqbiyjz 7Zom74bVhXChzMcGSPRrz6Zo9WQGfXJw72yxlVwqonPZx01OFdUr29Cz8qP1EjZ3r4xuVs QqChr/j91AcQU7EH2Kn3dikD3Y2b/OCQIB9zNEFqpjYi13OyPKJrNNK91BqYth6Yv2WyiR y6jccoaH3AkJgnlcXgmTt7xyYRVeZOBISgaj8LFQAfoj7TRoU+k4kMUELpi53w== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D264232 Kubilay Kocak changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ports-secteam@FreeBSD.org Keywords| |needs-patch, security Priority|--- |Normal --- Comment #10 from Kubilay Kocak --- 6.4.3 is affected by at least the following security vulnerabilities[1]: MMSA-2022-00112 MMSA-2022-00110 MMSA-2022-00109 MMSA-2022-00108 MMSA-2022-00104 (fixed in 6.4.3) MMSA-2022-00102 MMSA-2022-00101 6.3.x (LTS) received fixes for the above, but 6.4.x (non-LTS release) has n= ot (except MMSA-2022-00104) There are additional vulnerabilities for 6.5, 6.6, 6.7 [1] that were only f= ixed in 7.0, 7.1, 7.2 branches. There are upgrade compatibility considerations for every major.minor upstre= am=20 release [2], including schema and configuration changes that are required p= ost upgrade: 6.4 -> 6.6 comprises configuration only changes 6.7 has schema changes 7.1 has schema changes 7.2 has schema changes Current mattermost release branches [3] are: v7.3 - Feature Release v7.2 - Feature Release v7.1 - Extended Support Release v7.0 - Major Release v6.3 - Extended Support Release Options for upgrade paths given the above are: 1) Upgrade port to latest (supported) LTS, currently 7.1, OR 2) Upgrade port to latest version, currently 7.3, OR=20 3) Create new mattermost7 port(s), at the current LTS, allowing people upgrade at their own pace. Since Option 1 requires schema changes, Option 2 isn't much more of an issu= e. However, Option 2 puts the port in a position (at a non-LTS version) where = it could end up in the same situation as today, without support and not receiving bug or security fixes. Also, quarterly port/package versions are vulnerable, so any option must satisfy resolving in quarterly. Quarterly is not supposed to receive functional / feature changes (all else equal), particularly those that may break service/services on upgrade without user intervention. This leaves Option 3 as the most viable option, with the addition of: 3.1) Mark current mattermost ports DEPRECATED and vulnerable (VuXML), w= ith messaging to upgrade/move to the latest port version, with clear UPDATING upgrade instructions. 3.2) Merge the new mattermost7 port(s), allowing users in quarterly to upgrade with notice. A decent mattermost port/package target state would appear to be a mattermo= stX port for each major (X) version LTS (minor) version. In order to progress this issue, the following is necessary, in order: 1) VuXML patch adding each vulnerability including all vulnerable/fixed versions correctly. 2) Patch creating new mattermost7 port(s) for 7.1 LTS version 3) Patch marking current mattermost port as DEPRECATED with EXPIRATION_= DATE (fairly immediately) and clear messaging of what to do. 4) Patch to UPDATING adding clear information for what users need to do= for a 6.4.2 to 7.1 (new port) upgrade. 5) Remove current mattermost port in HEAD at some point, potentially wi= th MOVED (to mattermost7) entry (needs-qa). [1] https://mattermost.com/security-updates/ [2] https://docs.mattermost.com/upgrade/important-upgrade-notes.html [3] https://docs.mattermost.com/install/self-managed-changelog.html --=20 You are receiving this mail because: You are the assignee for the bug.=