Red Hat Bugzilla – Bug 983080
freerdp: freerdp: Multiple security fixes in 1.1.0-beta1 version [fedora-all]
Last modified: 2015-02-17 11:03:02 EST
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 creating a Bodhi update request, please use the bodhi submission link
noted 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
Bodhi notes field when available.
Please note: this issue affects multiple supported versions of Fedora.
Only one tracking bug has been filed; please ensure that it is only closed
when all affected versions are fixed.
[bug automatically created by: add-tracking-bugs]
Please use the following update submission link to create the Bodhi
request 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.
Please also ensure that the "Close bugs when update is stable" option
Bodhi update submission link:
The recently introduced beta1 version in Fedora 20/21 is already older by a few months and causes breakage for applications that link to freerdp 1.1.
A fix for this already exists in the last release:
(In reply to Simone Caronni from comment #2)
That is not a release, and trying to package it shows that it seems very incomplete and untested. It would benice if they could make a beta2.
(In reply to Mads Kiilerich from comment #3)
> (In reply to Simone Caronni from comment #2)
> > https://github.com/FreeRDP/FreeRDP/releases/tag/1.1.0-beta+2013071101
> That is not a release, and trying to package it shows that it seems very
> incomplete and untested. It would benice if they could make a beta2.
What would you count as a release? It's in their release folder:
And the first choice in their GitHub release page:
It is listed as a bugfix release for the one currently shipped in Fedora 20+; so I think it makes a much better candidate than the one currently shipping.
At the moment I need it to compile a package that links with FreeRDP 1.0 and the latest beta, but not in the middle:
Upstream Guacamole developer has stated that the bugs have been fixed in a more recent FreeRDP 1.1 version than the one currently in Fedora.
You are right. I had only seen that "release" as a tag.
/me wonders why they didn't call it beta2.
(In reply to Mads Kiilerich from comment #5)
> /me wonders why they didn't call it beta2.
Agree, worst way to call it probably...
So, it seems we still have a vulnerable version in Fedora?
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.