Red Hat Bugzilla – Bug 1291254
Rebase FreeRDP to newer version
Last modified: 2017-12-01 21:10:32 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
There is just a general connection error message
It asks user to accept or reject the changed certificate
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:
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.
*** Bug 1417798 has been marked as a duplicate of this bug. ***
Probably the latest info about the planned release can be found at:
However, it seems that there aren't any timelines yet...
Good news is that 2.0.0-rc0 has been finally released:
Let's move this in 7.6 since the stable release was not released yet...