Bug 1291254 - Rebase FreeRDP to newer version
Rebase FreeRDP to newer version
Status: NEW
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: freerdp (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Ondrej Holy
Desktop QE
: Rebase
: 1417798 (view as bug list)
Depends On:
Blocks: 1290449 1349566 1357558 983079
  Show dependency treegraph
Reported: 2015-12-14 07:40 EST by Marek Kašík
Modified: 2017-12-01 21:10 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Marek Kašík 2015-12-14 07:40:58 EST
Description of problem:
To be able to fix feature request from #1290449, we need to have newer FreeRDP available (at least 1.1). There is (*pVerifyChangedCertificate) callback defined in it which allows us to inform user about change of fingerprint of certificate of remote machine so that he can accept or reject the new certificate.

Steps to Reproduce:
1. Connect to remote Windows machine
2. Accept given certificate
3. Change fingerprint of the machine in ~/.freerdp/known_hosts to something else
4. Connect to the machine again

Actual results:
There is just a general connection error message

Expected results:
It asks user to accept or reject the changed certificate
Comment 1 Ondrej Holy 2016-01-07 03:28:00 EST
There is more bugs which will be fixed by the rebase. The problem is that freerdp-1.0 is latest official upstream stable release. Though there were 1.1 and 1.2 beta releases, but they have never been released as stable. Upstream told that current master (future 2.0) is most stable version ever, but release isn't scheduled yet...

Another problem might be that the public API was changed a lot since 1.0 version and also cmd syntax is different...

See some recent discussions on mailing list regarding to releases:
Comment 2 Ondrej Holy 2016-06-23 04:56:36 EDT
Upstream wants to make API freeze around July and then they want to work towards 2.0-rc1, see: 

So let's reconsider this for rhel-7.4.
Comment 3 Ondrej Holy 2017-02-06 07:39:53 EST
*** Bug 1417798 has been marked as a duplicate of this bug. ***
Comment 4 Ondrej Holy 2017-02-06 07:41:27 EST
Probably the latest info about the planned release can be found at:

However, it seems that there aren't any timelines yet...
Comment 5 Ondrej Holy 2017-07-28 05:14:04 EDT
Good news is that 2.0.0-rc0 has been finally released:
Comment 6 Ondrej Holy 2017-08-08 09:42:13 EDT
Let's move this in 7.6 since the stable release was not released yet...

Note You need to log in before you can comment on or make changes to this bug.