RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

> Current RHEL 8.3 package version:
2.1.1

> Future RHEL 8.4 package version:
2.2.0

> Is the RHEL 8.4 package version final or do we expect another additional update before the deadline for rebases (ITM 11)? If so, please tell us why.
I would like to rebase to the latest stable release which will be available at that time as I expect new security fixes to appear...

> Reasons why we are rebasing (security fixes/features (please specify)):
Especially because of the following security fixes: Bug 1868680, Bug 1855914, Bug 1855910, Bug 1855908, Bug 1855884, Bug 1855529, Bug 1855865, Bug 1855461, but it also contains some interesting bug fixes.

> Changelog between the old RHEL version and a new one:
See https://github.com/FreeRDP/FreeRDP/blob/stable-2.0/ChangeLog.

> What other RHEL packages will be affected by this rebase (rebased/tested)?
It might require a rebuild of Vinagre.

> Are there any risks related to the rebase?
The rebase is just within stable-2.0 branch, so I don't expect any issues.

> Additional comments:
No further comments.

Today I was quickly able to check Windows xp, windows 7 and windows10 without any issue.

freerdp-2.2.0-1.el8.x86_64

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: freerdp security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:1849