From owner-svn-src-user@FreeBSD.ORG Fri Apr 12 07:06:30 2013 Return-Path: Delivered-To: svn-src-user@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3B6FF2CF for ; Fri, 12 Apr 2013 07:06:30 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id A61EB1348 for ; Fri, 12 Apr 2013 07:06:29 +0000 (UTC) Received: (qmail 76284 invoked from network); 12 Apr 2013 08:13:27 -0000 Received: from c00l3r.networx.ch (HELO [127.0.0.1]) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 12 Apr 2013 08:13:27 -0000 Message-ID: <5167B26F.3020107@freebsd.org> Date: Fri, 12 Apr 2013 09:06:23 +0200 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: svn commit: r249365 - in user/andre/tcp-ao/sys: conf crypto crypto/cmac crypto/hmac crypto/rijndael References: <201304111555.r3BFtq0g019604@svn.freebsd.org> <5167A5DA.7050109@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: src-committers@freebsd.org, svn-src-user@freebsd.org X-BeenThere: svn-src-user@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the experimental " user" src tree" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Apr 2013 07:06:30 -0000 On 12.04.2013 09:04, Adrian Chadd wrote: > On 11 April 2013 23:12, Andre Oppermann wrote: > >> I don't know yet. It's still some time until the code is >> fully functional and tested. At runtime it wont have any >> impact until an application installs the first key on a >> tcp socket. > > I'm more worried about kernel size footprint with new features. It can easily be made a compile time option. > I may not want this enabled on some of the tiny embedded platforms. > Much like how I can't fit IPv6 into them at the present. :( Who needs IPv6 anyways? ;) -- Andre