Re: CURRENT: bhyve: xfreerdp doesn't support OpenSSL 3 yet. Alternatives?

On 29/06/23 16:35, FreeBSD User wrote:
> Hello,
> 
> running a recent CURRENT, 14.0-CURRENT #10 main-n263871-fd774e065c5d: Thu Jun 29 05:26:55 CEST
> 2023 amd64, xfreerdp (net/freerdp) doesn't working anymore on Windows 10 guest in bhyve. It
> seems OpenSSL 3 is the culprit (see the error message from xfreerdp below). I opened already a
> PR (see: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272281). In a very quick response I
> was informed that recent FreeRDP doesn't support OpenSSL 3 yes
> (https://github.com/FreeRDP/FreeRDP/pull/8920).
> 
> Checking for HowTo's setting up bhyve guests, I dodn't realise any setting for alternatives to
> RDP. As I do not fully understand how bhyve passes through its guest's framebuffer device/ or
> native GUI, I'm a bit helpless in searching for another solution to contact the Windows10
> guest from the X11 desktop of the hosts.
> 
> Trying remmina turns out to be a fail, because in our installation libsoup2 and libsoup3 are
> installed both and remmina complains about having both symbols, also I realised remmina seems
> to utilize net/freerdb as the RDP backend.
> 
> Since I have no clue how to install "blindly" a VNCserver within the Windows10 guest, I
> presume VNC is not an option in any way.
> 
> Is there any way to access the bhyve guest's native graphical interface? As in the PR shown
> above already documented (setup taken from the FreeBSD Wiki/bhyve), a framebuffer is already
> configured.
> 
> It would be nice if someone could give a hint.
> 

I had the same issue, with Windows 10 pro hosts, but the fault is in 
windows, which, by default, tries to negotiate an ancient protocol (NTLM 
using RC4 if I understand correctly).

With modern windows RDP servers there are better protocols available, 
you can get them in remmina by forcing "TLS protocolo security" in the 
advanced tab, security protocol negotiation (second row).

Doing this (after some experimentation with various options) solved the 
issue for me.

-- 
Guido Falsi <mad@madpilot.net>