Bug 1679685

Summary: [RFE] Kerberos support for FreeRDP
Product: Red Hat Enterprise Linux 9 Reporter: Chris Zinda <czinda>
Component: freerdpAssignee: Ondrej Holy <oholy>
Status: CLOSED MIGRATED QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: amike, jesse.thilo, ogutierr, oholy, rduda, sbarcomb, tpelka, tpopela, vpakolu
Target Milestone: rcKeywords: FutureFeature, MigratedToJIRA, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-15 19:14:17 UTC Type: Story
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1291254    
Bug Blocks:    

Description Chris Zinda 2019-02-21 16:17:25 UTC
Description of problem:

Environments that have FIPS enabled RHEL 7.x client and Windows server are unable to login using NLA.  In environments where NLA is required on the Windows Server side this means they cannot login via FreeRDP as the NTLM stack is using unsupported FIPS ciphers.

Version-Release number of selected component (if applicable):

freerdp-1.0.2-15.el7.x86_64.


How reproducible:

Very reproducible.


Steps to Reproduce:
1. Setup FIPS enabled Windows server
2. Setup FIPS enabled RHEL server
3. Enable NLA on Windows Server
4. Connect via freerdp

Actual results:

Connected to hostname.fqdn:3389
Connected to hostname.fqdn:3389
recv:  Connection reset by peer
Error:  protocol security negotiation failure.


Expected results:

Connect without issue.

Additional info:

The Windows Server is required to have NLA enabled because of the DISA STIG requirements.

Comment 4 Ondrej Holy 2019-02-26 08:35:28 UTC
This is not feasible for RHEL 7.7, but let's reconsider this for RHEL 7.8.

We are going to rebase to FreeRDP 2.0, which is prerequisite for this:
https://bugzilla.redhat.com/show_bug.cgi?id=1291254

but there are various issues with Kerberos implementation currently:
https://github.com/FreeRDP/FreeRDP/labels/kerberos

thus FreeRDP is built without Kerberos support, what was recommended by upstream developers.

Comment 20 Ondrej Holy 2023-03-16 12:37:41 UTC
Let’s summarize the current state of Kerberos in FreeRDP a bit. The experimental Kerberos support that is part of the 2.x releases never worked properly and had to be disabled. The "proper" Kerberos support is not part of any upstream releases yet, but it should be part of the next stable release. It is part of the master branch only, but there are still some unresolved Kerberos-related issues. The 3.0 release is currently planned for Q2/Q3 (https://sourceforge.net/p/freerdp/mailman/message/37780636/). It is impossible to backport this for 2.x releases, so we have to wait for the next stable release. And after it will be released, we will have to wait for some time before it will be properly tested. The FreeRDP package in RHEL 8 is classified under the ACG Compatibility level 2, so it can't be rebased there. Thus this has to be postponed to RHEL 9, where it is classified under the ACG Compatibility level 4.

Comment 21 RHEL Program Management 2023-09-15 19:13:52 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 22 RHEL Program Management 2023-09-15 19:14:17 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.