Date: Mon, 25 May 2026 10:19:55 -0700 From: Pete Wright <pete@nomadlogic.org> To: freeBSD-python@freebsd.org Subject: Best way to help get CVE's addressed Message-ID: <560c94dc-aa6a-4670-a3be-b89f1f2ce0ec@nomadlogic.org>
index | next in thread | raw e-mail
hello - i was hoping to find the best place to help address outstanding CVE's for python pkgs. i noticed charlie's last comment in this bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=294246#c20 i understand that it is a lot of effort to keep on top of these patches. since i run python systems for work i would like to do my fair share to help get these patched in a timely manner. my goal would be to have "pkg audit" be clean for my python webapp servers. i searched bugzilla and wasn't sure if we are filing reports for each CVE and tracking there, or are our efforts better spent focusing on getting a newer default python out the door? -pete -- Pete Wright pete@nomadlogic.orghome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?560c94dc-aa6a-4670-a3be-b89f1f2ce0ec>
