From owner-freebsd-current@freebsd.org Mon May 27 14:05:07 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2820C15975A8 for ; Mon, 27 May 2019 14:05:07 +0000 (UTC) (envelope-from voidanix@420blaze.it) Received: from cock.li (mx1.cock.li [185.10.68.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B8F176E518 for ; Mon, 27 May 2019 14:05:05 +0000 (UTC) (envelope-from voidanix@420blaze.it) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on cock.li X-Spam-Level: X-Spam-Status: No, score=-0.1 required=5.0 tests=BAYES_20,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,NO_RECEIVED,NO_RELAYS shortcircuit=_SCTYPE_ autolearn=disabled version=3.4.2 MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=420blaze.it; s=mail; t=1558965321; bh=5PMNdjjtSquhyMLhDVT88a8IBTFAHdzN0uznVR/WvVs=; h=Date:From:To:Subject:From; b=Lw33e+LV8wbo4aLnQKtvh9Jv0LxY9QF3rTOAdXgyRKtqEsQnJlyawpR2ayz5tFZxZ RRvAKLGt65SLq2IOy3q8IrKlK/LM7GyR0nFhTbf3fxUgED722ouH1gkMDpXenWZ5YG o1iFT+pg1/hq8EZbsDtYRL2ub9wlJMFrUB1cdH4S8+uYdanGCiD5MErt39F2Vt6OBH +0LQx3qxKmyJvwft2Hm07/unZGQeI+zDp7lUSQJg9T59eUYxEXl5w+3TMYZJuRuKSv C+/FSYlUDyuYhyTK1b624tVBKwPwKddJV2NXgCGPaiPHpprySl0ZeYI3jwHrpTsE3s DxieKRTYKhuJw== Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 27 May 2019 15:55:21 +0200 From: voidanix@420blaze.it To: freebsd-current@freebsd.org Subject: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option Message-ID: X-Sender: voidanix@420blaze.it User-Agent: Roundcube Webmail/1.3.6 X-Rspamd-Queue-Id: B8F176E518 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=420blaze.it header.s=mail header.b=Lw33e+LV; spf=pass (mx1.freebsd.org: domain of voidanix@420blaze.it designates 185.10.68.5 as permitted sender) smtp.mailfrom=voidanix@420blaze.it X-Spamd-Result: default: False [-4.10 / 15.00]; R_SPF_ALLOW(-0.20)[+mx]; TO_DN_NONE(0.00)[]; MX_GOOD(-0.01)[cached: mx1.cock.li]; DKIM_TRACE(0.00)[420blaze.it:+]; NEURAL_HAM_SHORT(-0.87)[-0.868,0]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; IP_SCORE(-0.72)[asn: 200651(-3.52), country: SC(-0.09)]; ASN(0.00)[asn:200651, ipnet:185.10.68.0/24, country:SC]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; R_DKIM_ALLOW(-0.20)[420blaze.it:s=mail]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[420blaze.it]; RCPT_COUNT_ONE(0.00)[1]; FROM_NO_DN(0.00)[]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Mon, 27 May 2019 14:05:07 -0000 Hello, I wanted to discuss about bug 231768 a bit: it is about keeping COMPAT_FREEBSD4/5/6/7/9 on by default in the kernel configs. The patch attached for the bug is for disabling these options by default, following a few reasons which I'm going to list here: - Keeping support for deprecated libraries isn't exactly the best we could do to avoid security issues (if there are any) as I'm sure nobody wants to spend that much time maintaining such stuff (it's enough to think about misc/compat4x in the ports tree: that version of FreeBSD was released on March 2000 and keeping 19 years old libraries around isn't ideal) - Devs should get track of time and realize that developing software using unsupported libraries is NOT something that you should do - Only a tiny fraction of the ports need COMPAT_FREEBSD9 or older: if the software won't compile without the legacy components (and has a replacement of some kind), considering removal wouldn't be a bad idea - This is on by default: most users don't care or don't use binaries that old I don't see any practical reason to keep these options on by default, but I do appreciate any sort of input regarding this issue. - voidanix