• Re: Status of Python 3.11

    From Dan Langille@dan@langille.org to muc.lists.freebsd.ports on Fri Aug 7 19:24:06 2026
    From Newsgroup: muc.lists.freebsd.ports

    On Wed, Jun 24, 2026, at 12:45 AM, Matthias Fechner wrote:
    Hi,

    Am 23.06.26 um 20:49 schrieb Nuno Teixeira:
    I see that https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285957 is
    staled.

    I'm unsure if it is the right time to start doing local builds with 3.13.


    I switched now to 3.13 and all seems at first to run fine.
    Will test it the next days.

    I have been using Python 3.14 for some time and have switched over from 3.12

    Two issues vex me and the alerts are overwhelming.

    CVE-2025-15367
    CVE-2025-15366

    Every host is alerts with those, some for over 70 days.

    Alert fatigue is a real thing.

    I yearn for a way to easily silence specific vulns in the output of pkg-audit. I'm all for recording in vuxml. Yet at the same time, I want relief from pages of red alerts and having to scan them all to see if there's anything new.
    --
    Dan Langille
    dan@langille.org


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=@des@FreeBSD.org to muc.lists.freebsd.ports on Sat Aug 8 02:17:33 2026
    From Newsgroup: muc.lists.freebsd.ports

    "Dan Langille" <dan@langille.org> writes:
    Two issues vex me and the alerts are overwhelming.

    CVE-2025-15367
    CVE-2025-15366
    Patches for these exist, but the maintainer refuses to apply them. https://reviews.freebsd.org/D57717
    https://reviews.freebsd.org/D57718
    DES
    --
    Dag-Erling Sm|+rgrav - des@FreeBSD.org
    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Edward Sanford Sutton, III@mirror176@hotmail.com to muc.lists.freebsd.ports on Sat Aug 8 13:55:06 2026
    From Newsgroup: muc.lists.freebsd.ports

    On 8/7/26 16:24, Dan Langille wrote:
    On Wed, Jun 24, 2026, at 12:45 AM, Matthias Fechner wrote:
    Hi,

    Am 23.06.26 um 20:49 schrieb Nuno Teixeira:
    I see that https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285957 is
    staled.

    I'm unsure if it is the right time to start doing local builds with 3.13. >>

    I switched now to 3.13 and all seems at first to run fine.
    Will test it the next days.

    I have been using Python 3.14 for some time and have switched over from 3.12

    Two issues vex me and the alerts are overwhelming.

    CVE-2025-15367
    CVE-2025-15366

    Every host is alerts with those, some for over 70 days.

    Alert fatigue is a real thing.

    I yearn for a way to easily silence specific vulns in the output of pkg-audit. I'm all for recording in vuxml. Yet at the same time, I want relief from pages of red alerts and having to scan them all to see if there's anything new.

    Until such a useful feature is added, you could self-filter one way
    or another:

    pkg audit >~/vuln.old
    # edit list to contain only vulnerabilities you do not care about
    pkg audit -F >~/vuln.new
    # a simple general output
    diff ~/vuln.*|egrep "^<"|less
    # an easily modified general output, in case you want it to help
    # you review things you can now remove.
    diff -y ~/vuln.*|egrep ">"|less

    You can end up with a short name script or alias that does the
    fetch+diff.
    Alternatively you can maintain your own vulnerability database
    variation where you apply select removals and rebuild with other new
    changes as they come along.
    Its easy to find yourself in a situation where a vulnerability is not relevant, but if another relevant vulnerability is used then preexisting vulnerability threats should be reconsidered.
    I's also find it helpful if we could run a check against the current
    pkg repo, and separately against the ports tree, to see if current
    versions include any fixes. I normally do that one port at a time by
    taking `pkg audit -q` output as a list of packages to check and running
    a series of repeats of it with an additional parameter like

    pkg audit -q `make -C /usr/ports/\`pkg query %o python311-3.11.15_4\` -VPKGNAME`

    I should probably script that too but never got around to it and just manually pass the few names in, usually as a variable set at the start
    or a separate command for easy editing.


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Li@vishwin@freebsd.org to muc.lists.freebsd.ports on Sat Aug 8 18:01:49 2026
    From Newsgroup: muc.lists.freebsd.ports

    This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------sfFhFZ0eLGACjHsY0pvu5iUW
    Content-Type: multipart/mixed; boundary="------------wOrtJTF6vfprJnGzavMYUjB5";
    protected-headers="v1"; hp="clear"
    Message-ID: <0d971157-8a8d-49b0-8759-f58db4067bea@freebsd.org>
    Date: Sat, 8 Aug 2026 18:01:49 -0400
    MIME-Version: 1.0
    User-Agent: Mozilla Thunderbird
    Subject: Re: Status of Python 3.11
    To: Jochen Neumeister <joneum@FreeBSD.org>,
    =?UTF-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@FreeBSD.org>,
    Dan Langille <dan@langille.org>
    Cc: Matthias Fechner <idefix@fechner.net>, Nuno Teixeira
    <eduardo@freebsd.org>, Xavier Humbert <xavier@groumpf.org>,
    freebsd-ports <freebsd-ports@freebsd.org>
    References: <aac0d288-ccd7-47ab-9826-d34794323522@groumpf.org>
    <86eci2v3c1.fsf@ltc.des.dev> <86v7bet9ik.fsf@ltc.des.dev>
    <86ik7dtacm.fsf@ltc.des.dev>
    <9e94cf7f-5af7-40f4-9d2c-3cee1b793bff@fechner.net>
    <86pl1hpc3p.fsf@ltc.des.dev>
    <62d314f2-c30f-4740-9ef4-20be14973baa@fechner.net>
    <CAFDf7ULYhTan_m5s3bESpdy+xOuuP82MsQ-tRA2QnpBWicLohg@mail.gmail.com>
    <c9670059-cc72-495f-bd8e-911f68e3ec47@fechner.net>
    <77c043ff-dbd0-4ea8-9acc-b884dddf9688@app.fastmail.com>
    <86ik5l8nz6.fsf@ltc.des.dev>
    <84952088-0ef8-46c3-af65-1bfe98de26aa@FreeBSD.org>
    Content-Language: en-GB
    From: Charlie Li <vishwin@freebsd.org>
    Autocrypt: addr=vishwin@freebsd.org; keydata=
    xjMEaEicoBYJKwYBBAHaRw8BAQdAZBuydpjFLGem4uRJPWaYMXX2e+BN1jDhbD3tcqbxhdfN
    MkNoYXJsaWUgTGkgKEZyZWVCU0QgUHJvamVjdCkgPHZpc2h3aW5ARnJlZUJTRC5vcmc+wpkE
    ExYKAEEWIQTHxcCLnAXo3rFg6k7P+1cn7slqBAUCaEicoAIbAwUJCWYBgAULCQgHAgIiAgYV
    CgkICwIEFgIDAQIeBwIXgAAKCRDP+1cn7slqBM/bAP9bhA4e0LxJYFYJlftZM5WHrMSPpUe6
    G2pVqmQWTQ0EZQEA0PNryfH3qRWWPSI8mFNRnG24hi5/aXFqCnHj1tcJ9Q/OOARoSJygEgor
    BgEEAZdVAQUBAQdAUT4TzYFmV6ueIGwjX0N+445KZV6ns1Wiw67QMsJZxHkDAQgHwn4EGBYK
    ACYWIQTHxcCLnAXo3rFg6k7P+1cn7slqBAUCaEicoAIbDAUJCWYBgAAKCRDP+1cn7slqBPO/
    AQCPuGiyyfJClICRs/ToG0MsT8YcPdBygzuUIIeGpkjJpgEA7AoFCQ0Y28Y3hIDFn2k9PH3B
    nGWL3g05W0ds2qoj+gQ=
    Organization: FreeBSD Project
    In-Reply-To: <84952088-0ef8-46c3-af65-1bfe98de26aa@FreeBSD.org>

    --------------wOrtJTF6vfprJnGzavMYUjB5
    Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64

    Sm9jaGVuIE5ldW1laXN0ZXIgd3JvdGU6DQo+IA0KPiANCj4gQW0gMDguMDguMjYgdW0gMDI6 MTcgc2NocmllYiBEYWctRXJsaW5nIFNtw7hyZ3JhdjoNCj4+ICJEYW4gTGFuZ2lsbGUiIDxk YW5AbGFuZ2lsbGUub3JnPiB3cml0ZXM6DQo+Pj4gVHdvIGlzc3VlcyB2ZXggbWUgYW5kIHRo ZSBhbGVydHMgYXJlIG92ZXJ3aGVsbWluZy4NCj4+Pg0KPj4+IENWRS0yMDI1LTE1MzY3DQo+ Pj4gQ1ZFLTIwMjUtMTUzNjYNCj4+DQo+PiBQYXRjaGVzIGZvciB0aGVzZSBleGlzdCwgYnV0 IHRoZSBtYWludGFpbmVyIHJlZnVzZXMgdG8gYXBwbHkgdGhlbS4NCj4+DQo+PiBodHRwczov L3Jldmlld3MuZnJlZWJzZC5vcmcvRDU3NzE3DQo+PiBodHRwczovL3Jldmlld3MuZnJlZWJz ZC5vcmcvRDU3NzE4DQo+Pg0KPiBBcyBhIG1lbWJlciBvZiB0aGUgcG9ydHMtc2VjdGVhbSwg SSBoYXZlIGFza2VkIGZvciBhIHByb21wdCByZXNvbHV0aW9uLiANCj4gSSBoYXZlIGxlZnQg YSBjb21tZW50IHRvIHRoaXMgZWZmZWN0IGluIGVhY2ggcmV2aWV3Lg0KPiANCk5vdGhpbmcg d2lsbCBiZSBiYWNrcG9ydGVkIHVudGlsIHVwc3RyZWFtIGNhbiB2ZXJpZnkgdGhhdCB0aGUg Zml4ZXMgZG8gDQpub3QgYnJlYWsgZXhpc3RpbmcgKGNvcnJlY3QpIGJlaGF2aW91ci4gQ3Vy cmVudGx5IG9ubHkgdGhlIGltYXBsaWIgDQooQ1ZFLTIwMjUtMTUzNjYpIGZpeGVzIGFyZSBw cmVzZW50IGluIHRoZSBsYXRlc3QgdXBzdHJlYW0gDQpsYW5nL3B5dGhvbjMxezMsNCw1fS4N Cg0KLS0gDQpDaGFybGllIExpDQouLi5ub3BlLCBzdGlsbCBkb24ndCBoYXZlIGFuIGV4aXQg bGluZS4NCg==

    --------------wOrtJTF6vfprJnGzavMYUjB5--

    --------------sfFhFZ0eLGACjHsY0pvu5iUW
    Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature
    Content-Disposition: attachment; filename="OpenPGP_signature.asc"

    -----BEGIN PGP SIGNATURE-----

    wnoEABYIACMWIQTHxcCLnAXo3rFg6k7P+1cn7slqBAUCanenTQUDAAAAAAAKCRDP+1cn7slqBNpK APiv/LdP+tAs+xWR6EUewgY0x/mL8ixRdqjOWNoxSUvHAP418vfYbLKfKyiTD8L4A6JZck0hkdCi ZT9VPGS2tRa2AA==
    =TcGV
    -----END PGP SIGNATURE-----

    --------------sfFhFZ0eLGACjHsY0pvu5iUW--


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=@des@FreeBSD.org to muc.lists.freebsd.ports on Sun Aug 9 08:27:23 2026
    From Newsgroup: muc.lists.freebsd.ports

    Charlie Li <vishwin@freebsd.org> writes:
    Nothing will be backported until upstream can verify that the fixes do
    not break existing (correct) behaviour. Currently only the imaplib (CVE-2025-15366) fixes are present in the latest upstream lang/python31{3,4,5}.
    Not true. The patches I posted _are_ from upstream 3.15. There is an additional commit to imaplib commit which we could include:
    commit d0921efb665aff26b378f495e5ff84f7e3fe649d
    Author: Serhiy Storchaka <storchaka@gmail.com>
    AuthorDate: Sun Jul 5 18:25:36 2026 +0300
    Commit: GitHub <noreply@github.com>
    CommitDate: Sun Jul 5 18:25:36 2026 +0300
    gh-143921: Narrow the control character check in imaplib commands (GH-153067)

    Only NUL, CR and LF are rejected now. Other control characters are
    valid in quoted strings and can occur in mailbox names returned by
    the server, so they are now accepted and sent quoted.

    Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
    Upstream 3.13.15 and 3.14.7 already have both imaplib patches but not
    the poplib patch.
    DES
    --
    Dag-Erling Sm|+rgrav - des@FreeBSD.org
    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Dan Mahoney (Ports)@freebsd@gushi.org to muc.lists.freebsd.ports on Tue Aug 11 03:17:18 2026
    From Newsgroup: muc.lists.freebsd.ports

    To Dan's L's point, though.
    This is stupid. Python3.11 is supported for security fixes for another year-plus. It's got an active 2025 CVE with what looks like a reasonable fix, even if "unofficial".
    Blocking on "we can't accept the changes unless upstream says they're okay" -- upstream thinks "the code we have, with the active CVE" is okay, otherwise they would have, yanno, put out a new release. Because it's still supported. Otherwise, that statement about support and EOL dates is meaningless.
    Yes, developer fatigue is a thing, god knows I've hit it myself when Life Happened.
    And yeah, pkg-audit needs a knob that exempts specific CVEID's/vuxml entries/packages from its alert. If you've looked at your system, read the tea leaves, asked other knowledgeable people, asked your favorite LLM, and asked your magic 8 ball and you say "okay, this is an imap and pop3 vuln, I am sure I'm not using those libs" OR "I have patched the code that consumes those functions" OR "in fact I've deleted them post-install, let me go on with life", you should be able to.
    -Dan
    On Aug 8, 2026, at 11:27rC>PM, Dag-Erling Sm|+rgrav <des@FreeBSD.org> wrote:

    Charlie Li <vishwin@freebsd.org> writes:
    Nothing will be backported until upstream can verify that the fixes do
    not break existing (correct) behaviour. Currently only the imaplib
    (CVE-2025-15366) fixes are present in the latest upstream
    lang/python31{3,4,5}.

    Not true. The patches I posted _are_ from upstream 3.15. There is an additional commit to imaplib commit which we could include:

    commit d0921efb665aff26b378f495e5ff84f7e3fe649d
    Author: Serhiy Storchaka <storchaka@gmail.com>
    AuthorDate: Sun Jul 5 18:25:36 2026 +0300
    Commit: GitHub <noreply@github.com>
    CommitDate: Sun Jul 5 18:25:36 2026 +0300

    gh-143921: Narrow the control character check in imaplib commands (GH-153067)

    Only NUL, CR and LF are rejected now. Other control characters are
    valid in quoted strings and can occur in mailbox names returned by
    the server, so they are now accepted and sent quoted.

    Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

    Upstream 3.13.15 and 3.14.7 already have both imaplib patches but not
    the poplib patch.

    DES
    --
    Dag-Erling Sm|+rgrav - des@FreeBSD.org

    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Dan Langille@dan@langille.org to muc.lists.freebsd.ports on Tue Aug 11 07:20:38 2026
    From Newsgroup: muc.lists.freebsd.ports

    On Tue, Aug 11, 2026, at 6:17 AM, Dan Mahoney wrote:
    To Dan's L's point, though.

    [snip]

    And yeah, pkg-audit needs a knob that exempts specific CVEID's/vuxml entries/packages from its alert. If you've looked at your system, read
    the tea leaves, asked other knowledgeable people, asked your favorite
    LLM, and asked your magic 8 ball and you say "okay, this is an imap and
    pop3 vuln, I am sure I'm not using those libs" OR "I have patched the
    code that consumes those functions" OR "in fact I've deleted them post-install, let me go on with life", you should be able to.

    Please my post to freebsd-ports@ titled "modifying pkg-audit to ignore specified vulns"

    re: https://lists.freebsd.org/archives/freebsd-ports/2026-August/009871.html

    I have done a manual proof-of-concept and now it's just a simple matter of coding.
    --
    Dan Langille
    dan@langille.org


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Dan Langille@dan@langille.org to muc.lists.freebsd.ports on Tue Aug 11 10:50:41 2026
    From Newsgroup: muc.lists.freebsd.ports

    On Tue, Aug 11, 2026, at 8:25 AM, Piotr Smyrak wrote:
    On Tue, 11 Aug 2026 07:20:38 -0400
    "Dan Langille" <dan@langille.org> wrote:

    On Tue, Aug 11, 2026, at 6:17 AM, Dan Mahoney wrote:
    To Dan's L's point, though.

    [snip]

    And yeah, pkg-audit needs a knob that exempts specific
    CVEID's/vuxml entries/packages from its alert. If you've looked at
    your system, read the tea leaves, asked other knowledgeable people,
    asked your favorite LLM, and asked your magic 8 ball and you say
    "okay, this is an imap and pop3 vuln, I am sure I'm not using those
    libs" OR "I have patched the code that consumes those functions" OR
    "in fact I've deleted them post-install, let me go on with life",
    you should be able to.

    Please my post to freebsd-ports@ titled "modifying pkg-audit to
    ignore specified vulns"

    re:
    https://lists.freebsd.org/archives/freebsd-ports/2026-August/009871.html

    I have done a manual proof-of-concept and now it's just a simple
    matter of coding.

    Dan,

    IIUC, you are building your own packages. I would like to propose a
    simpler approach that does not require any development whatsoever.
    You could either patch the local ports tree or just revert the
    commits that added these vulnerabilities to the XML file, and
    build the VuXML DB from such patched port, publish the XML artifact to
    be accessible from within Freshports network, and modify this setting in pkg.conf:

    #VULNXML_SITE = "http://vuxml.freebsd.org/freebsd/vuln.xml.xz";

    This way you just redirect the whole infrastructure to a custom
    advisory DB, still built and relying on a slightly adjusted project DB.

    As long as you don't push from this local git repo of ports, you can
    even commit the change. (I am assuming here, you use git to fetch the
    tree).

    That is a nice idea. Thank you. That helps me, definitely.

    The "tricky" part may be knowing there is a new VuXML to build and then distributing it.

    I'm an outlier. Most people do not build their own.
    --
    Dan Langille
    dan@langille.org


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Piotr Smyrak@ps.ports@smyrak.com to muc.lists.freebsd.ports on Tue Aug 11 20:47:12 2026
    From Newsgroup: muc.lists.freebsd.ports

    On Tue, 11 Aug 2026 10:50:41 -0400
    "Dan Langille" <dan@langille.org> wrote:

    On Tue, Aug 11, 2026, at 8:25 AM, Piotr Smyrak wrote:
    On Tue, 11 Aug 2026 07:20:38 -0400
    "Dan Langille" <dan@langille.org> wrote:

    On Tue, Aug 11, 2026, at 6:17 AM, Dan Mahoney wrote:
    To Dan's L's point, though.

    [snip]

    And yeah, pkg-audit needs a knob that exempts specific
    CVEID's/vuxml entries/packages from its alert. If you've looked
    at your system, read the tea leaves, asked other knowledgeable
    people, asked your favorite LLM, and asked your magic 8 ball and
    you say "okay, this is an imap and pop3 vuln, I am sure I'm not
    using those libs" OR "I have patched the code that consumes
    those functions" OR "in fact I've deleted them post-install, let
    me go on with life", you should be able to.

    Please my post to freebsd-ports@ titled "modifying pkg-audit to
    ignore specified vulns"

    re:
    https://lists.freebsd.org/archives/freebsd-ports/2026-August/009871.html >>
    I have done a manual proof-of-concept and now it's just a simple
    matter of coding.

    Dan,

    IIUC, you are building your own packages. I would like to propose a
    simpler approach that does not require any development whatsoever.
    You could either patch the local ports tree or just revert the
    commits that added these vulnerabilities to the XML file, and
    build the VuXML DB from such patched port, publish the XML artifact
    to be accessible from within Freshports network, and modify this
    setting in pkg.conf:

    #VULNXML_SITE = "http://vuxml.freebsd.org/freebsd/vuln.xml.xz";

    This way you just redirect the whole infrastructure to a custom
    advisory DB, still built and relying on a slightly adjusted project
    DB.

    As long as you don't push from this local git repo of ports, you can
    even commit the change. (I am assuming here, you use git to fetch
    the tree).

    That is a nice idea. Thank you. That helps me, definitely.

    The "tricky" part may be knowing there is a new VuXML to build and
    then distributing it.

    You could setup a git hook that detects changes to the XML files in security/vuxml/vuln and triggers a rebuild of your own DB.

    I'm an outlier. Most people do not build their own.

    To me this is the FreeBSD spirit!
    --
    Piotr Smyrak


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Gert Doering@gert@greenie.muc.de to muc.lists.freebsd.ports on Tue Aug 11 20:58:31 2026
    From Newsgroup: muc.lists.freebsd.ports

    Hi,

    On Tue, Aug 11, 2026 at 08:47:12PM +0200, Piotr Smyrak wrote:
    IIUC, you are building your own packages. I would like to propose a simpler approach that does not require any development whatsoever.
    You could either patch the local ports tree or just revert the
    commits that added these vulnerabilities to the XML file, and
    build the VuXML DB from such patched port, publish the XML artifact
    to be accessible from within Freshports network, and modify this
    setting in pkg.conf:

    #VULNXML_SITE = "http://vuxml.freebsd.org/freebsd/vuln.xml.xz";
    [..]
    You could setup a git hook that detects changes to the XML files in security/vuxml/vuln and triggers a rebuild of your own DB.

    This is not really the way to address CVE alert fatigue for people
    that do not want to hack around the alerting system by building their
    own stuff left and right.

    Most of my machines do not build anything locally, or even have a ports
    or source tree checked out (using binpkg and freebsd-update saves quite
    a significant bit of CPU = power = co2 costs...). So having something
    that tells daily-security "ignore these two vulns, please" would be
    much more useful for me.

    gert
    --
    "If was one thing all people took for granted, was conviction that if you
    feed honest figures into a computer, honest figures come out. Never doubted
    it myself till I met a computer with a sense of humor."
    Robert A. Heinlein, The Moon is a Harsh Mistress

    Gert Doering - Munich, Germany gert@greenie.muc.de


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Piotr Smyrak@ps.ports@smyrak.com to muc.lists.freebsd.ports on Wed Aug 12 11:11:13 2026
    From Newsgroup: muc.lists.freebsd.ports

    Hello,

    On Tue, 11 Aug 2026 20:58:31 +0200
    Gert Doering <gert@greenie.muc.de> wrote:

    On Tue, Aug 11, 2026 at 08:47:12PM +0200, Piotr Smyrak wrote:
    IIUC, you are building your own packages. I would like to
    propose a simpler approach that does not require any
    development whatsoever. You could either patch the local ports
    tree or just revert the commits that added these
    vulnerabilities to the XML file, and build the VuXML DB from
    such patched port, publish the XML artifact to be accessible
    from within Freshports network, and modify this setting in
    pkg.conf:

    #VULNXML_SITE = "http://vuxml.freebsd.org/freebsd/vuln.xml.xz";

    [..]
    You could setup a git hook that detects changes to the XML files in security/vuxml/vuln and triggers a rebuild of your own DB.

    This is not really the way to address CVE alert fatigue for people
    that do not want to hack around the alerting system by building their
    own stuff left and right.

    Of course. And I agree with you. Still this is a voluntary free software project. So despite patches being welcome, they may not come ready
    tomorrow.

    And by this proposal I am merely trying to help Dan lift some burden of
    his back. Hopefully until the patches are in place.

    Most of my machines do not build anything locally, or even have a
    ports or source tree checked out (using binpkg and freebsd-update
    saves quite a significant bit of CPU = power = co2 costs...). So
    having something that tells daily-security "ignore these two vulns,
    please" would be much more useful for me.

    In test reporting there is a concept of an expected fail, or
    acknowledged one, and certain monitoring systems allow for flipping
    such forever failing test item into green by marking it as such. Which
    may as well in future turn red when it stops failing and thus then
    needs to be turned around again.

    What I am trying to say above is that the approach may also depend on
    what monitoring tool one uses.
    --
    Piotr Smyrak


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Gert Doering@gert@greenie.muc.de to muc.lists.freebsd.ports on Wed Aug 12 12:52:08 2026
    From Newsgroup: muc.lists.freebsd.ports

    Hi,

    On Wed, Aug 12, 2026 at 11:11:13AM +0200, Piotr Smyrak wrote:
    This is not really the way to address CVE alert fatigue for people
    that do not want to hack around the alerting system by building their
    own stuff left and right.

    Of course. And I agree with you. Still this is a voluntary free software project. So despite patches being welcome, they may not come ready
    tomorrow.

    I understand. Just trying to bring other perspectives to the table.

    (While I do understand "ports" and "vuxml" halfway by now, I'm not sure
    I understand the FreeBSD shell script magic sufficiently to contribute
    here)

    [..]
    In test reporting there is a concept of an expected fail, or
    acknowledged one, and certain monitoring systems allow for flipping
    such forever failing test item into green by marking it as such. Which
    may as well in future turn red when it stops failing and thus then
    needs to be turned around again.

    What I am trying to say above is that the approach may also depend on
    what monitoring tool one uses.

    "daily mail with security and pkg audit included"... (daily_status_security_pkgaudit_enable=YES)

    gert
    --
    "If was one thing all people took for granted, was conviction that if you
    feed honest figures into a computer, honest figures come out. Never doubted
    it myself till I met a computer with a sense of humor."
    Robert A. Heinlein, The Moon is a Harsh Mistress

    Gert Doering - Munich, Germany gert@greenie.muc.de


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2