From owner-freebsd-python@freebsd.org Tue Sep 24 03:07:19 2019 Return-Path: Delivered-To: freebsd-python@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2C716F549D for ; Tue, 24 Sep 2019 03:07:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 46cmMC05R1z3Qvb for ; Tue, 24 Sep 2019 03:07:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id EDF23F549A; Tue, 24 Sep 2019 03:07:18 +0000 (UTC) Delivered-To: python@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id EDBDFF5499 for ; Tue, 24 Sep 2019 03:07:18 +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) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46cmMB4CDlz3QvY for ; Tue, 24 Sep 2019 03:07:18 +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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 7242320E70 for ; Tue, 24 Sep 2019 03:07:18 +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 x8O37IJH026181 for ; Tue, 24 Sep 2019 03:07:18 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x8O37IKM026171 for python@FreeBSD.org; Tue, 24 Sep 2019 03:07:18 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: python@FreeBSD.org Subject: [Bug 240774] security/py-fido2: Update to 0.7.1 Date: Tue, 24 Sep 2019 03:07:18 +0000 X-Bugzilla-Reason: CC 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: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: grembo@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: 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 MIME-Version: 1.0 X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Sep 2019 03:07:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D240774 --- Comment #10 from Kubilay Kocak --- (In reply to Michael Gmelin from comment #8) And yeh, security vulnerabilities are almost always High/Many, unless the vulnerability is conditional on an option (say a port option or optional or non-standard configuration). In the security vulnerability case, there's a = case to 'leaning towards' Many/High, independent of the underlying nature, given= the 'importance' of that class of issue The question ultimately however, is less a function of what to label what, = but more about how to label things in a manner that makes it *most* valuable to= the project/developers to optimize limited resources (time/effort), ie; the principle purpose of 'prioritization'. In our issue tracking, we make little to no use of prioritization. One contributor to that I theorize is an aversion to the term given its use in commercial/PHB settings, along with 'in a project of volunteers you cant ha= ve expectations'. And unfortunately, those perceptions/mindsets have knock on effects beyond issue tracking and across the board: degree to which everything committed is reviewed, testing, code/commit message quality/standards/formatting, documentation, changelogs, etc. --=20 You are receiving this mail because: You are on the CC list for the bug.=