Description of problem: A windows patch broke version 0.rc0.1_mga6 but version 2.0.0-rc2 fixes the problem. By replacing FreeRDP-2.0.0-rc0.tar.gz with FreeRDP-2.0.0-rc2.tar.gz in rpmbuild/SOURCES, tweaking the spec file and rebuilding fixes the problem. Tested in Mageia 6 x86_64. rdesktop still works if until freerdp is patched. Version-Release number of selected component (if applicable): 2.0.0-0.rc0.1. How reproducible: Always with a system that has had KB4088776 applied. Steps to Reproduce: 1. Find patched windows system. 2. Attempt to connect. 3. The error message "ERRCONNECT_PASSWORD_CERTAINLY_EXPIRED" is returned and the connection fails.
Assigning to the registered maintainer.
Assignee: bugsquad => geiger.david68210CC: (none) => marja11
Assigning to QA, Advisory: ============================= Our current freerdp package can't connect to a recently patched windows system, this issue was fixed upstream in freerdp 2.0.0 RC2. So this update fixes this issue. ============================= Packages in 6/core/updates_testing: ======================== freerdp-2.0.0-0.rc2.1.mga6.x86_64.rpm lib64freerdp2-2.0.0-0.rc2.1.mga6.x86_64.rpm lib64freerdp-devel-2.0.0-0.rc2.1.mga6.x86_64.rpm freerdp-2.0.0-0.rc2.1.mga6.i586.rpm ibfreerdp2-2.0.0-0.rc2.1.mga6.i586.rpm libfreerdp-devel-2.0.0-0.rc2.1.mga6.i586.rpm Source RPM: ======================== freerdp-2.0.0-0.rc2.1.mga6.src.rpm
Assignee: geiger.david68210 => qa-bugs
MGA6-32 on Dell Latitude D600 MATE No installation issues Installed first 2.0.0-0.rc0.1. and at CLI: $ xfreerdp /v:<winlaptop> /u:<username> /p:<passwd> get error ERRCONNECT_SECURITY_NEGO_CONNECT_FAILED , which is not the same as Alan reported. Will test the update shortly.
CC: (none) => herman.viaene
Updated freerdp gives same error. I can ping the <winlaptop>, but I cannot ssh into it (time out). I have to find out the network or firewall settings of this machine
Info: the winlaptop is a Win10 Home edition and that does not support RDP.
64-bit installed properly, but currently do not have any window servers to test this against. installed without issue Attempted for remote assistance module in Win7/10, but could not establish a connection
CC: (none) => brtians1
I tried freerdp-2.0.0-0.rc2.1.mga6.x86_64.rpm and lib64freerdp2-2.0.0-0.rc2.1.mga6.x86_64.rpm from updates_testing and they worked correctly on a server 2008 and Windows 10. These rpm work as well as the ones I built. They certainly work better than freerdp-2.0.0.0-git20161228.3.
Started with : $ rpm -qa | grep freerdp lib64freerdp2-2.0.0-0.rc0.1.mga6 freerdp-2.0.0-0.rc0.1.mga6 rdp to a freshly updated windows 10 vm resulted in: $ xfreerdp /size:80% 10.189.16.174 [07:12:35:011] [12205:12205] [WARN][com.freerdp.client.common.cmdline] - Using deprecated command-line interface! [07:12:35:011] [12205:12205] [WARN][com.freerdp.client.common.compatibility] - 10.189.16.174 -> /v:10.189.16.174 [07:12:35:011] [12205:12205] [WARN][com.freerdp.client.common.compatibility] - [07:12:35:011] [12205:12206] [INFO][com.freerdp.client.x11] - No user name set. - Using login name: mrambo Domain: . Password: [07:12:41:410] [12205:12206] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_PASSWORD_CERTAINLY_EXPIRED [0x0002000F] [07:12:41:410] [12205:12206] [ERROR][com.freerdp.core.transport] - BIO_read returned an error: error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error [07:12:41:410] [12205:12206] [ERROR][com.freerdp.client.x11] - Freerdp connect error exit status 1 Manually downloaded and installed the update. $ sudo urpmi ./freerdp-2.0.0-0.rc2.1.mga6.x86_64.rpm ./lib64freerdp2-2.0.0-0.rc2.1.mga6.x86_64.rpm After updating I was able to again connect to the windows 10 vm. The update looks good to me on mga6 x86_64.
Whiteboard: (none) => MGA6-64-OKCC: (none) => mrambo
Ran the same test in a 32 bit mga6 vm. Results both before and after the update were identical so the 32 bit variant also looks good to me.
Whiteboard: MGA6-64-OK => MGA6-64-OK MGA6-32-OK
Thanks to all testers; nice surprise that people had the required systems. Advisoried, validated.
Keywords: (none) => advisory, validated_updateCC: (none) => sysadmin-bugs
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2018-0065.html
Status: NEW => RESOLVEDResolution: (none) => FIXED
Apparently this issue actually got a CVE: CVE-2018-0886. http://lists.suse.com/pipermail/sle-security-updates/2019-January/005053.html https://bugzilla.suse.com/show_bug.cgi?id=1085416
(In reply to David Walser from comment #12) > Apparently this issue actually got a CVE: CVE-2018-0886. > > http://lists.suse.com/pipermail/sle-security-updates/2019-January/005053.html > https://bugzilla.suse.com/show_bug.cgi?id=1085416 https://lists.opensuse.org/opensuse-updates/2019-01/msg00100.html
CC: (none) => luigiwalser