Bug 1266230 - freerdp doesn't handle server redirection
freerdp doesn't handle server redirection
Product: Fedora
Classification: Fedora
Component: freerdp (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Mads Kiilerich
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-09-24 16:15 EDT by Samuel Sieb
Modified: 2016-07-19 14:01 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-07-19 14:01:15 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
fix redirect handling (1.04 KB, patch)
2015-09-24 16:15 EDT, Samuel Sieb
no flags Details | Diff

  None (edit)
Description Samuel Sieb 2015-09-24 16:15:55 EDT
Created attachment 1076694 [details]
fix redirect handling

FreeRDP aborts connecting when receiving a redirect command from some versions of windows.  This is because it's expecting a certain amount of padding, but windows just closes the connection.  These patches have just been applied to master, but if there's not going to be an updated version in Fedora soon, it would be nice to get this patch applied.

Without the patch, as soon as you pass the login screen, freerdp just exits with no warning.
Comment 1 Fedora End Of Life 2016-07-19 14:01:15 EDT
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.

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