Bug 1052396
Summary: | libinfinity-0.5.5 is available | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> |
Component: | libinfinity | Assignee: | Till Maas <opensource> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | opensource, pabs3 |
Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | libinfinity-0.5.5-1.fc20 | Doc Type: | Enhancement |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-04-15 15:43:31 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Upstream Release Monitoring
2014-01-13 18:40:23 UTC
libinfinity-0.5.5-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/libinfinity-0.5.5-1.fc19 libinfinity-0.5.5-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/libinfinity-0.5.5-1.fc20 Package libinfinity-0.5.5-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing libinfinity-0.5.5-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-0792/libinfinity-0.5.5-1.fc20 then log in and leave karma (feedback). libinfinity-0.5.5-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. libinfinity-0.5.5-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. Why didn't this issue receive a CVE? (In reply to Paul Wise (Debian) from comment #6) > Why didn't this issue receive a CVE? I assumed this would happen by upstream or the security response team. I sent a mail to MITRE to request a CVE now. In general it is best to send CVE requests for public issues in FLOSS to the oss-security list. http://oss-security.openwall.org/wiki/disclosure/cve http://oss-security.openwall.org/wiki/mailing-lists/oss-security (In reply to Paul Wise (Debian) from comment #8) > In general it is best to send CVE requests for public issues in FLOSS to the > oss-security list. > > http://oss-security.openwall.org/wiki/disclosure/cve > http://oss-security.openwall.org/wiki/mailing-lists/oss-security I will remember it for the next time. This is now tracked as CVE-2014-2910. |