Am Fri, 30 Jun 2023 16:45:52 +0200
Pierre Pronchery schrieb:
My apology for the delay.
Shortly after the post here and several patches the problem vanished into thin
air - alos by
using tigervnc as the client and not, as proposed on the FreeBSD Wiki page,
xfreerdp.
Thank you very much for
Hi everyone,
I believe I understand where the issue loading OpenSSL's
legacy provider comes from (for MD4 support) and I am currently working
on a fix here:
https://github.com/khorben/freebsd-src/tree/khorben/openssl-3.0-providers
Basically the OpenSSL provider module for
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
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
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
> >
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
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
