From owner-freebsd-current@freebsd.org Wed Feb 3 08:49:38 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id F1933530077 for ; Wed, 3 Feb 2021 08:49:38 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (vogon.madpilot.net [159.69.1.99]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DVwNK72Fhz3nbW for ; Wed, 3 Feb 2021 08:49:37 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 4DVwNB3Slxz6dQR; Wed, 3 Feb 2021 09:49:30 +0100 (CET) Received: from mail.madpilot.net ([192.168.254.3]) by mail (mail.madpilot.net [192.168.254.3]) (amavisd-new, port 10026) with ESMTP id e3dUrLW38qNx; Wed, 3 Feb 2021 09:49:28 +0100 (CET) Subject: Re: (n244517-f17fc5439f5) svn stuck forever in /usr/ports? To: "Hartmann, O." , Rick Macklem Cc: FreeBSD CURRENT , "junchoon@dec.sakura.ne.jp" References: <20210130073923.0b2a80c1@hermann.fritz.box> <20210130192520.e7cf7f680c0abd31b0771107@dec.sakura.ne.jp> <18e15d74-d95b-76b7-59a4-64a8f338ba73@madpilot.net> <20210131103510.30d9a322@hermann.fritz.box> <86a368dc-f118-79fb-2ed8-af461041198a@madpilot.net> <20210203071608.1c2118b6@hermann.fritz.box> From: Guido Falsi Message-ID: Date: Wed, 3 Feb 2021 09:49:27 +0100 In-Reply-To: <20210203071608.1c2118b6@hermann.fritz.box> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4DVwNK72Fhz3nbW X-Spamd-Bar: / X-Spamd-Result: default: False [-1.00 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[159.69.1.99:from]; R_DKIM_ALLOW(-0.20)[madpilot.net:s=bjowvop61wgh]; MID_RHS_MATCH_FROM(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; TO_DN_SOME(0.00)[]; MISSING_MIME_VERSION(2.00)[]; FROM_HAS_DN(0.00)[]; MIME_GOOD(-0.10)[text/plain]; R_SPF_ALLOW(-0.20)[+mx]; ARC_NA(0.00)[]; SPAMHAUS_ZRD(0.00)[159.69.1.99:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[madpilot.net:+]; DMARC_POLICY_ALLOW(-0.50)[madpilot.net,quarantine]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:24940, ipnet:159.69.0.0/16, country:DE]; RCVD_TLS_LAST(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Feb 2021 08:49:39 -0000 On 03/02/21 07:16, Hartmann, O. wrote: > On Mon, 1 Feb 2021 03:24:45 +0000 > Rick Macklem wrote: > >> Rick Macklem wrote: >>> 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. >> I was wrong on the above. I did a full buildworld/installworld and the daemons >> now seem to work with the openssl in head/main. >> >> Btw, did anyone try rebuilding svn from sources after doing >> the system upgrade? >> (The openssl library calls and .h files definitely changed.) > > Yes, I did, on all boxes and its a pain in the a..., we had to rebuild EVERY port (at > least, I did, to avoid further problem). Yesterday, on of our fastes boxes got ready and > even with a full rebuild of the system AND a full rebuild of the ports (no poudriere, > traditional way via make), the Apache 2.4 webservice doesn't work, and so does subversion > not (Firefox reports problems with SSL handshake, subversion is stuck/frozen forever). > I will run today another full world build today, hopefully finishing on friday (portmaster > -dfR doesn't get everything in line on some ports, I assume). Ass I said a confirmed woraround is building world with WITHOUT_OPENSSL_KTLS defined. -- Guido Falsi