X-Original-To: bind9-public@bugs.isc.org References: From each@isc.org Wed Nov 29 19:44:45 2017 X-RT-Original-Encoding: utf-8 User-Agent: Mutt/1.5.23 (2014-03-12) Delivered-To: bind9-public@bugs.isc.org Content-Disposition: inline MIME-Version: 1.0 Received: from bikeshed.isc.org (bikeshed.isc.org [149.20.48.19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by bugs.isc.org (Postfix) with ESMTPS id C5E6CD78B0A for ; Wed, 29 Nov 2017 19:44:45 +0000 (UTC) Received: by bikeshed.isc.org (Postfix, from userid 10292) id 62960216C1C; Wed, 29 Nov 2017 19:44:45 +0000 (UTC) Subject: Re: [ISC-Bugs #46729] Drop seccomp support From: "Evan Hunt" Return-Path: CC: X-RT-Interface: Email Date: Wed, 29 Nov 2017 19:44:45 +0000 Message-ID: <20171129194445.GC35419@isc.org> X-RT-Incoming-Encryption: Not encrypted To: "Michał Kępień via RT" In-Reply-To: content-type: text/plain; charset="utf-8" RT-Message-ID: Content-Length: 734 > Removal is planned to be announced in > BIND 9.12.0 release notes and then performed in the next .0 release. My only quibble is let's not put the announcement in the 9.12.0 release notes. It's not the sort of thing we've done in release notes before, I think people might find it confusing, and if we remove any other featuers in 9.13 they might start asking why we didn't preannounce our intention to do *that*. If we want to preannounce removal, let's do so on bind-announce like we did with lwresd and XP support. I'm sold on the actual removal. If Logan wants to take a run at his privilege separation idea and send us a patch, we can consider the idea then; I don't see a need to keep the existing code until that happens.