From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 5B773158083 for ; Thu, 26 Sep 2024 00:19:40 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 44728E2A06; Thu, 26 Sep 2024 00:19:29 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183]) (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) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id D80C7E29F2 for ; Thu, 26 Sep 2024 00:19:28 +0000 (UTC) Received: by stitch (Postfix, from userid 1000) id 24364CB393; Wed, 25 Sep 2024 20:19:38 -0400 (EDT) Date: Wed, 25 Sep 2024 20:19:38 -0400 From: Michael Orlitzky To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Wayland! Beware of! Message-ID: References: <65e5de50-e053-46ff-be61-52f472d95025@gentoo.org> <6af6d0dd-f081-4345-b574-ea6d6c9358bb@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <6af6d0dd-f081-4345-b574-ea6d6c9358bb@gentoo.org> X-Archives-Salt: e5316251-f560-4898-99e1-9ccddb636dfc X-Archives-Hash: 3557c844f1ee140158c1a1e8b7dab17a On 2024-09-24 21:42:23, Eli Schwartz wrote: > > Please do not disable the USE=ipv6, as that is *utterly* insane. It also > does approximately nothing. In packages which support this USE flag, > which is rare, it causes the code to use old, untested APIs which only > support ipv4, rather than new, tested APIs that support ipv4 and ipv6 > equally well while having the benefit of being stable, reliable and > efficient. I think this greatly depends on the package. djbdns is fresh on my mind, and djbdns[ipv6] will pull in a massive third-party patch to add support for serving ipv6 records. The changes are so pervasive that (a) they required manually re-rolling several ipv4 security patches, and (b) may reintroduce some of the same security issues over ipv6, if nobody is filing CVEs against the patch. It's not clear-cut, but you can certainly argue that you're better off without USE=ipv6 if you're not serving ipv6 records. Pkgcheck has been warning about "bad" instances of USE=ipv6 for some time now. The longer the warning stays in place, the more packages we can expect to import some special useful meaning to it.