On Tue, Nov 3, 2020 at 11:39 AM Marek Marczykowski-Górecki <
marma...@invisiblethingslab.com> wrote:

> On Tue, Nov 03, 2020 at 10:02:24AM +0000, P J P wrote:
> > * Right, Fedora package CVEs and relevant bugs are filed by Red Hat
> Product security team.
> >
> > * CVEs/bugs are fixed in the upstream sources first. Fedora package
> maintainers do rebuild
> >   of the package with released fixes.
>
> I see currently over 1000 such tracking bugs[1].
> I realize it some cases it may be missing upstream fix and it is not a
> Fedora package maintainers responsibility to develop a fix (although
> anyone can help upstream to develop a fix). But by looking at few random
> items there, it seems the fix is available in a subsequent upstream
> release and what is missing is just bumping the package version in
> Fedora. In some (many?) cases, the newer package is even already there,
> but the missing part is closing related tracking bug (and I'd guess the
> update lacked info it was a security fix, but I haven't verified that).
>
>
I'm definitely guilty of the latter part, particularly for Node.js.

Generally, whenever Node.js issues a security release, they do so for
multiple issues simultaneously. When Product Security then goes and creates
Bugzilla tickets, they create many (sometimes up to five bugs per CVE). It
becomes nearly impossible to keep up with the bug maintenance in such
situations. The process is just too heavyweight and I often end up just
doing the upstream releases and ignoring the BZs.

If we want this to be more accurate, we really need to have a more
streamlined and/or automated solution for these issues.
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Reply via email to