From owner-svn-src-all@freebsd.org Sun Jul 5 20:04:09 2015 Return-Path: Delivered-To: svn-src-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A7BC7A477 for ; Sun, 5 Jul 2015 20:04:09 +0000 (UTC) (envelope-from bms@fastmail.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 75C21149E for ; Sun, 5 Jul 2015 20:04:09 +0000 (UTC) (envelope-from bms@fastmail.net) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 7C7502016C for ; Sun, 5 Jul 2015 16:04:01 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Sun, 05 Jul 2015 16:04:01 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=NfSnQqdtE0U3ifP8GD72xXOhmCY=; b=WTwEd/ crtShslOqCyCHYmHoj/PgQqd4W++e/2cRaSJZMR0ZmOP9zedftWltOKCvxiiz7I2 NVDnpSlWUdzz2R8h1YkWdMkEOhsDUGfVJjQWH+srq4XBzf3dWEhkgp+FUpGKSDsl J2M2TZ6QM1KyL9CPRGANKML+aUIXGxlFzQss0= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=NfSnQqdtE0U3ifP 8GD72xXOhmCY=; b=KM+HAtYqANjVRqBJKjxrqw7pMDlICdghAY0KZ0+YG+V1QQD 2lXiUJAQefgZOV6L6alGs6/OMPnmYw/ghPaqagI1y79//FYOOYdTQHJkjw7I/4QH NNxbLchQSFCdsbO1EnuVZlGVomuwtuE7GWI1lf3c4BRSpxSRSfPdCj006TOk= X-Sasl-enc: 4Fm1stot6V/eD34cTIyZr1tWLoWKjZPj6mgMhPOPxHZG 1436126641 Received: from pion.local (robtfraser.plus.com [80.229.9.145]) by mail.messagingengine.com (Postfix) with ESMTPA id 81F1B680180; Sun, 5 Jul 2015 16:04:00 -0400 (EDT) Message-ID: <55998DAF.2000609@fastmail.net> Date: Sun, 05 Jul 2015 21:03:59 +0100 From: Bruce Simpson User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: John-Mark Gurney CC: src-committers , svn-src-all@freebsd.org, Ian Lepore , "svn-src-head@freebsd.org" Subject: Re: svn commit: r285160 - head/sys/conf References: <201507051415.t65EFxWd044357@repo.freebsd.org> <20150705194954.GA8523@funkthat.com> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jul 2015 20:04:09 -0000 On 05/07/15 20:53, Oliver Pinter wrote: >>> Log: >>> Ensure all the required files get built when you include the IPSEC >>> option. +1. IETF position these days is that IPSEC should be a "standard feature". Key management is a separate issue, and support for newer ciphers like ChaCha20 (see NaCL by Daniel Bernstein et al) and authenticated encryption schemes please. >> Umm.. This looks more like that IPSEC should require that the crypto >> device be specified instead of fixing it this way... +1. Expressing static dependencies at the granularity of "file" rather than "module" or "subsystem" is a PITA, and leads to having to depth-first enumerate the deps like this, introducing clutter. > Is there any way to specify implication rules to config? > Ergo if I specify IPSEC without device crypto, then it's auto enable/include. > Similar to linux's Kconfig framework.. +1. I know this can be done at "module" granularity, but I have always found the "options" and "files" syntax somewhat arcane. I almost always copy-paste-edit existing stanzas.