This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
Use the following template to for the 'fedpkg update' request to submit an
update for this issue as it contains the top-level parent bug(s) as well as
this tracking bug. This will ensure that all associated bugs get updated
when new packages are pushed to stable.
# bugfix, security, enhancement, newpackage (required)
# low, medium, high, urgent (required)
# testing, stable
# Bug numbers: 1234,9876
# Description of your update
notes=Security fix for [PUT CVEs HERE]
# Enable request automation based on the stable/unstable karma thresholds
# Automatically close bugs when this marked as stable
# Suggest that users restart after update
Additionally, you may opt to use the bodhi web interface to submit updates:
I guess this is supposed to be tracking bug for this CVE(I guess that the other Dec's CVEs will apply too) in the golang container, right?
If it is it, needs to be against "Fedora Container Images/golang". Anyway I will rebuilt it. It is already on my todo.
(In reply to Jakub Čajka from comment #2)
> I guess this is supposed to be tracking bug for this CVE(I guess that the
> other Dec's CVEs will apply too) in the golang container, right?
> If it is it, needs to be against "Fedora Container Images/golang". Anyway I
> will rebuilt it. It is already on my todo.
Nope, this was an attempt to create tracker for golang-1.10.3 that is shipped in the golang:1.1 module in Fedora 29.
It's unclear if that was really meant to be released given that there's non-modular 1.11, but it is definitely out there.
There's also golang:1.10 in Fedora 28.
(In reply to Tomas Hoger from comment #3)
> (In reply to Jakub Čajka from comment #2)
> > I guess this is supposed to be tracking bug for this CVE(I guess that the
> > other Dec's CVEs will apply too) in the golang container, right?
> > If it is it, needs to be against "Fedora Container Images/golang". Anyway I
> > will rebuilt it. It is already on my todo.
> Nope, this was an attempt to create tracker for golang-1.10.3 that is
> shipped in the golang:1.1 module in Fedora 29.
> It's unclear if that was really meant to be released given that there's
> non-modular 1.11, but it is definitely out there.
Ah.. ok. I will take a look at that too.
Added new parent flaw bug 1657564 (CVE-2018-16874), 1657565 (CVE-2018-16875) to this tracking bug.
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 29 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.