The 13th of March, Microsoft released some Service Pack, ie KB4088776 [1] that brakes FreeRDP and consequently all the software using FreeRDP, like Remmina, Vinagre, KRDC, etc. The FreeRDP team has fixed the problem via the commit https://github.com/FreeRDP/FreeRDP/pull/4487/commits/e7ae3f6babc881d893411a5ada9156abe8525b2f Therefore, without this fix, all the client applications using FreeRDP, won't be able to connect to these Windows versions that have the Service Pack specified between the brackets. Windows 10 (KB4088776) Windows Server 2016 (KB4088787) Windows 8.1 (KB4088876) Windows Server 2012 R2 (KB4088876) Windows 7 SP1 (KB4088875) Windows Server 2008 R2 SP1 (KB4088875) Is it possible to update both software, FreeRDP and Remmina to the latest commits available? I don't know if Vinagre and KRDC needs to be updated as well. Thanks in advance!!!! [1] https://support.microsoft.com/en-us/help/4088776/windows-10-update-kb4088776
Assign to freerdp maintainer and Cc: remmina maintainer.
Hi, I'm out of town until Sunday/Monday timeframe- I'll be able to work on this at that point.
Thank you, no problem, if you need help let me know. In our wiki we have a simple and not very well curated procedure we use to build both https://github.com/FreeRDP/Remmina/wiki/Compile-on-FreeBSD Sorry for the bad quality...
I've pushed some fixes in the main Remmina branch (named next) that fixes some issues with the Gnome integration. I should not have any other fixes to push, but I'll confirm EOD or tomorrow morning as the latest. Thanks again!
I built this against git revision: 103686e I updated the patch-ffmpeg29 and patch-winpr_libwinpr_utils_ssl.c to work with that revision. Attached. However, it fails to connect with the error: com.winpr.synch.timer] - InitializeWaitableTimer: os specific implementation is missing
Created attachment 191646 [details] patch-ffmpeg29 file
Created attachment 191647 [details] patch-winpr_libwinpr_utils.ssl.c file
Okay. way too many changes between rc1 and now. I backported the patch for nla.c and it now works based off the rc1 already in ports. Ignore the ffpmeg and libwinpr patch. Attached is the nla.c patch.
Created attachment 191650 [details] nla.c patch This builds and works for me off the current 2.0.0-rc1 port.
(In reply to Antenore Gatta from comment #4) > I've pushed some fixes in the main Remmina branch (named next) that fixes some issues with the Gnome integration. > > I should not have any other fixes to push, but I'll confirm EOD or tomorrow morning as the latest. > I confirm that the latest commit available as today [1], can be considered stable. [1] https://unix.stackexchange.com/questions/207907/how-to-fix-gpg-key-retrieval-failed-errno-14#207985
(In reply to Antenore Gatta from comment #10) Sorry, wrong URL Commit: 5f3cc40be2bc1d3d92f0db7cc14affbf0eef4297 https://github.com/FreeRDP/Remmina/commit/5f3cc40be2bc1d3d92f0db7cc14affbf0eef4297
Hi, Just FYI- I have a ports tree patch prepared [1] to backport the fix to -rc1 and bump PORTREVISION on remmina-plugin-rdp and vinagre; this fixes the problem for me. I'd rather wait on updating the port until we can coax FreeRDP folk into releasing an -rc2. I'm working on getting this committed. [1] https://people.freebsd.org/~kevans/freerdp-patch.diff
A commit references this bug: Author: kevans Date: Wed Mar 21 14:04:06 UTC 2018 New revision: 465177 URL: https://svnweb.freebsd.org/changeset/ports/465177 Log: net/freerdp: Fix following recent Windows update, bump dependents Patch backported from upstream @ fbe01c7; breakage seems to be that FreeRDP will emit an error "ERRCONNECT_PASSWORD_CERTAINLY_EXPIRED" in a context where one is certain that that is not the case. PR: 226651 Approved by: brd (ports), me (maintainer) Changes: head/net/freerdp/Makefile head/net/freerdp/files/patch-libfreerdp_core_nla.c head/net/remmina-plugin-rdp/Makefile head/net/vinagre/Makefile
Thanks Kyle!
Has the problem been solved, with this commit? Then the PR can be closed.
For me it's ok, can be closed.
Does this need to be merged to the 2018Q2 ports branch also?
Nope- we got it in before 2018Q2 branched and I failed to close it. =)
Great - thanks Kyle!