Date: Sun, 31 Jan 2021 22:01:57 +0000 From: Rick Macklem <rmacklem@uoguelph.ca> To: "Hartmann, O." <ohartmann@walstatt.org>, FreeBSD CURRENT <freebsd-current@freebsd.org>, Guido Falsi <mad@madpilot.net> Cc: "junchoon@dec.sakura.ne.jp" <junchoon@dec.sakura.ne.jp> Subject: Re: (n244517-f17fc5439f5) svn stuck forever in /usr/ports? Message-ID: <YQXPR0101MB0968D09A38D0A8E244D8C2C6DDB79@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM> In-Reply-To: <86a368dc-f118-79fb-2ed8-af461041198a@madpilot.net> References: <20210130073923.0b2a80c1@hermann.fritz.box> <20210130192520.e7cf7f680c0abd31b0771107@dec.sakura.ne.jp> <18e15d74-d95b-76b7-59a4-64a8f338ba73@madpilot.net> <a5e18e3b-181c-c094-b98c-7e233cdac972@madpilot.net> <20210131103510.30d9a322@hermann.fritz.box>, <86a368dc-f118-79fb-2ed8-af461041198a@madpilot.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Guido Falsi wrote: [good stuff snipped] >Performed a full bisect. Tracked it down to commit aa906e2a4957, adding >KTLS support to embedded OpenSSL. > >I filed a bug report about this: > >https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253135 > > >Apart from switching to svn:// scheme, another workaround is to build >base using WITHOUT_OPENSSL_KTLS. Just fyi, when I tested the daemons I have for nfs-over-tls (which use ktls), they acted like things were ok (no handshake problems), but the data ended up on the wire unencrypted (nfs-over-tls doesn't do a SSL_write(), so it depends on ktls to do the encryption). Since these daemons work fine with openssl3 in ports/security/openssl-devel, I suspect the ktls backport is not quite right. I've sent jhb@ email. rick -- Guido Falsi <mad@madpilot.net> _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YQXPR0101MB0968D09A38D0A8E244D8C2C6DDB79>