Source: freerdp Version: 1.1.0~git20140921.1.440916e+dfsg1-5 Severity: normal Tags: upstream patch
It seems there's a bug with connecting to certain Windows Server hosts w/ certain configurations. Upstream has already fixed the issue, and I've supplied a version of the patch that should apply to the version Debian maintains. The issue has to do with null certificates and Windows Server 2003 R2 hosts (and possibly others). A null certificate is not an error-condition, though it was being handled as such (and it seems the error handling has also been improved upstream, given the bug report and the messages I was seeing w/ Debian's version). Relevant GitHub (FreeRDP/FreeRDP) issue: https://github.com/FreeRDP/FreeRDP/issues/1795 and related commit/patch: https://github.com/FreeRDP/FreeRDP/commit/603a6378fffd43a67e14ead860bcf9196be6979e Thanks! -- Nate -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
577,578c577,578 < if (length < 4) < return -1; --- > if (length < 4) /* NULL certificate is not an error see #1795 */ > return 1;
