On Jun 29, 2023 at 11:36 AM -0500, FreeBSD User , wrote:
> Am Thu, 29 Jun 2023 16:41:51 +0200
> Guido Falsi schrieb:
>
> > 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 202
On 29/06/23 18:34, FreeBSD User wrote:
Am Thu, 29 Jun 2023 16:41:51 +0200
Guido Falsi schrieb:
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 anym
Am Thu, 29 Jun 2023 16:41:51 +0200
Guido Falsi schrieb:
> 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
> > 1
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 xf
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 (se