From owner-freebsd-arch@FreeBSD.ORG Sun Nov 16 02:20:13 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C734F16A4CE for ; Sun, 16 Nov 2003 02:20:13 -0800 (PST) Received: from gw.celabo.org (gw.celabo.org [208.42.49.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F75D43F93 for ; Sun, 16 Nov 2003 02:20:11 -0800 (PST) (envelope-from nectar@celabo.org) Received: from madman.celabo.org (madman.celabo.org [10.0.1.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "madman.celabo.org", Issuer "celabo.org CA" (verified OK)) by gw.celabo.org (Postfix) with ESMTP id 030C35489C; Sun, 16 Nov 2003 04:20:11 -0600 (CST) Received: by madman.celabo.org (Postfix, from userid 1001) id 851C36D455; Sun, 16 Nov 2003 04:20:10 -0600 (CST) Date: Sun, 16 Nov 2003 04:20:10 -0600 From: "Jacques A. Vidrine" To: Terry Lambert Message-ID: <20031116102010.GA53282@madman.celabo.org> Mail-Followup-To: "Jacques A. Vidrine" , Terry Lambert , freebsd-arch@freebsd.org References: <20031114194119.GA94198@madman.celabo.org> <3FB6AA8F.37ED6D50@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FB6AA8F.37ED6D50@mindspring.com> X-Url: http://www.celabo.org/ User-Agent: Mutt/1.5.4i-ja.1 cc: freebsd-arch@freebsd.org Subject: Re: __TIME_MIN/__TIME_MAX X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Nov 2003 10:20:13 -0000 On Sat, Nov 15, 2003 at 02:37:03PM -0800, Terry Lambert wrote: > "Jacques A. Vidrine" wrote: > > In at least one place in libc, it is necessary to range check a time_t > > value. One most platforms, time_t has the same range as `int', but > > on at least amd64, it has a larger range. Any objections to adding > > definitions of __TIME_MIN and __TIME_MAX to sys/${arch}/_limits.h? > > > > I could just do the usual check for lossage after casting, except that > > in theory time_t could be a floating-point value (but not in reality > > in FreeBSD). It seems cleaner to me to have an explicit range. > > XSI: time_t and clock_t shall be integer or real-floating types. > > The range should be derived from th type. Defining separate values > outside the implementation namespace might be OK, but keeping those > values synchronized with the size_t is likely to be painful for > years to come. I don't think I understand your point. time_t and size_t have no relationship. The __TIME_MIN/__TIME_MAX I was suggesting would have been analogous to other numerical limits defined in such as INT_MIN/INT_MAX or our implementation-only __OFF_MIN/__OFF_MAX. Yes, they'd need to be synchronized with the actual type in use, e.g. #define __TIME_MAX __INT_MAX /* most platforms */ #define __TIME_MAX __LONG_MAX /* ia64, amd64 */ (Note that now, I don't intend to implement this because it doesn't actually help me get out of the quandry I was in. But, I still feel like discussing if anyone is interested :-) By the way, that quote from SUSv3 (``shall be integer or real-floating types'') is what messes me up. time_t could be signed or unsigned. If it were unsigned (extremely unlikely, but OK according to the letter of the standard), then I don't think I can detect certain range errors. /* How can this be implemented correctly? */ int range_error(long n, time_t t) { return (long)(t = n) == n; } Too bad (IMHO) C never grew other operators like sizeof that let you examine type attributes. Cheers, -- Jacques Vidrine NTT/Verio SME FreeBSD UNIX Heimdal nectar@celabo.org jvidrine@verio.net nectar@freebsd.org nectar@kth.se From owner-freebsd-arch@FreeBSD.ORG Sun Nov 16 03:12:14 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D5C016A4CE for ; Sun, 16 Nov 2003 03:12:14 -0800 (PST) Received: from gw.celabo.org (gw.celabo.org [208.42.49.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C36643FA3 for ; Sun, 16 Nov 2003 03:12:13 -0800 (PST) (envelope-from nectar@celabo.org) Received: from madman.celabo.org (madman.celabo.org [10.0.1.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "madman.celabo.org", Issuer "celabo.org CA" (verified OK)) by gw.celabo.org (Postfix) with ESMTP id 0CCC95482B; Sun, 16 Nov 2003 05:12:13 -0600 (CST) Received: by madman.celabo.org (Postfix, from userid 1001) id 9B0976D455; Sun, 16 Nov 2003 05:12:12 -0600 (CST) Date: Sun, 16 Nov 2003 05:12:12 -0600 From: "Jacques A. Vidrine" To: Terry Lambert , freebsd-arch@freebsd.org Message-ID: <20031116111212.GA55844@madman.celabo.org> Mail-Followup-To: "Jacques A. Vidrine" , Terry Lambert , freebsd-arch@freebsd.org References: <20031114194119.GA94198@madman.celabo.org> <3FB6AA8F.37ED6D50@mindspring.com> <20031116102010.GA53282@madman.celabo.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031116102010.GA53282@madman.celabo.org> X-Url: http://www.celabo.org/ User-Agent: Mutt/1.5.4i-ja.1 Subject: Re: __TIME_MIN/__TIME_MAX X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Nov 2003 11:12:14 -0000 On Sun, Nov 16, 2003 at 04:20:10AM -0600, Jacques A. Vidrine wrote: > /* How can this be implemented correctly? */ > int range_error(long n, time_t t) > { > return (long)(t = n) == n; > } Hrmp. Because time_t is probably signed, technically this can cause `undefined behavior' if the range of `long' is more than the range of `time_t' (e.g. on alpha). *sigh* All I really want to do is correct a parsing bug and at the same time eliminate a warning so that I can set WARNS?=1 in libc before the code freeze. Cheers, -- Jacques Vidrine NTT/Verio SME FreeBSD UNIX Heimdal nectar@celabo.org jvidrine@verio.net nectar@freebsd.org nectar@kth.se From owner-freebsd-arch@FreeBSD.ORG Sun Nov 16 04:36:48 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31EF816A4CE; Sun, 16 Nov 2003 04:36:48 -0800 (PST) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C15343F93; Sun, 16 Nov 2003 04:36:46 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3p2/8.8.7) with ESMTP id XAA04395; Sun, 16 Nov 2003 23:36:42 +1100 Date: Sun, 16 Nov 2003 23:36:41 +1100 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: "Jacques A. Vidrine" In-Reply-To: <20031116111212.GA55844@madman.celabo.org> Message-ID: <20031116231838.X1400@gamplex.bde.org> References: <20031114194119.GA94198@madman.celabo.org> <3FB6AA8F.37ED6D50@mindspring.com> <20031116111212.GA55844@madman.celabo.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-arch@FreeBSD.org Subject: Re: __TIME_MIN/__TIME_MAX X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Nov 2003 12:36:48 -0000 On Sun, 16 Nov 2003, Jacques A. Vidrine wrote: > On Sun, Nov 16, 2003 at 04:20:10AM -0600, Jacques A. Vidrine wrote: > > /* How can this be implemented correctly? */ > > int range_error(long n, time_t t) > > { > > return (long)(t = n) == n; > > } > > Hrmp. Because time_t is probably signed, technically this can cause > `undefined behavior' if the range of `long' is more than the range of > `time_t' (e.g. on alpha). *sigh* Actually, it's implementation-defined if time_t is integral (doesn't matter if it is signed or unsigned) (and the value is not representable). It's only undefined if time_t is a floating type. > All I really want to do is correct a parsing bug and at the same time > eliminate a warning so that I can set WARNS?=1 in libc before the code > freeze. You can safely assume that it won't change to floating before the code freeze :-). I think (t = n) would cause compiler warnings at higher WARNS levels if time_t were unsigned. `t == n' certainly would. `(long)(time_t)n == n' could be used (this is like the above except it doesn't use a temporary variable. However, the cast to long breaks the warning about the bug that if n is -1L and time_t is unsigned long, then the comarison will succeed on 2's complement machines although time_t cannot represent -1. Bruce From owner-freebsd-arch@FreeBSD.ORG Sun Nov 16 04:52:32 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2155A16A4CE for ; Sun, 16 Nov 2003 04:52:32 -0800 (PST) Received: from gw.celabo.org (gw.celabo.org [208.42.49.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1515F43FB1 for ; Sun, 16 Nov 2003 04:52:31 -0800 (PST) (envelope-from nectar@celabo.org) Received: from madman.celabo.org (madman.celabo.org [10.0.1.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "madman.celabo.org", Issuer "celabo.org CA" (verified OK)) by gw.celabo.org (Postfix) with ESMTP id AE2D35482B; Sun, 16 Nov 2003 06:52:30 -0600 (CST) Received: by madman.celabo.org (Postfix, from userid 1001) id 53AAA6D455; Sun, 16 Nov 2003 06:52:30 -0600 (CST) Date: Sun, 16 Nov 2003 06:52:30 -0600 From: "Jacques A. Vidrine" To: Bruce Evans Message-ID: <20031116125230.GA56115@madman.celabo.org> Mail-Followup-To: "Jacques A. Vidrine" , Bruce Evans , Terry Lambert , freebsd-arch@FreeBSD.org References: <20031114194119.GA94198@madman.celabo.org> <3FB6AA8F.37ED6D50@mindspring.com> <20031116102010.GA53282@madman.celabo.org> <20031116111212.GA55844@madman.celabo.org> <20031116231838.X1400@gamplex.bde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031116231838.X1400@gamplex.bde.org> X-Url: http://www.celabo.org/ User-Agent: Mutt/1.5.4i-ja.1 cc: freebsd-arch@FreeBSD.org Subject: Re: __TIME_MIN/__TIME_MAX X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Nov 2003 12:52:32 -0000 On Sun, Nov 16, 2003 at 11:36:41PM +1100, Bruce Evans wrote: > Actually, it's implementation-defined if time_t is integral (doesn't > matter if it is signed or unsigned) (and the value is not representable). > It's only undefined if time_t is a floating type. Are you certain? I'll have to double-check. I thought that if a type was signed, then attempting to assign an out-of-range value was undefined (similar to overflow with signed types). > > > All I really want to do is correct a parsing bug and at the same time > > eliminate a warning so that I can set WARNS?=1 in libc before the code > > freeze. > > You can safely assume that it won't change to floating before the code > freeze :-). Heh. Until a few hours ago, I was pretty sure that no one would dare make any changes to time_t this late in the game, but then the sparc64 time_t thread sprouted. :-) > I think (t = n) would cause compiler warnings at higher WARNS levels > if time_t were unsigned. `t == n' certainly would. > `(long)(time_t)n == n' could be used (this is like the above except it > doesn't use a temporary variable. However, the cast to long breaks the > warning about the bug that if n is -1L and time_t is unsigned long, then > the comarison will succeed on 2's complement machines although time_t > cannot represent -1. The actual warning was of the `comparison always true' variety. Annoying, but it did lead me to see that there was a (mostly harmless) bug in strptime. Cheers, -- Jacques Vidrine NTT/Verio SME FreeBSD UNIX Heimdal nectar@celabo.org jvidrine@verio.net nectar@freebsd.org nectar@kth.se From owner-freebsd-arch@FreeBSD.ORG Sun Nov 16 05:00:59 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D976516A4CE for ; Sun, 16 Nov 2003 05:00:59 -0800 (PST) Received: from gw.celabo.org (gw.celabo.org [208.42.49.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C5DF43FCB for ; Sun, 16 Nov 2003 05:00:58 -0800 (PST) (envelope-from nectar@celabo.org) Received: from madman.celabo.org (madman.celabo.org [10.0.1.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "madman.celabo.org", Issuer "celabo.org CA" (verified OK)) by gw.celabo.org (Postfix) with ESMTP id 26652548A4; Sun, 16 Nov 2003 07:00:58 -0600 (CST) Received: by madman.celabo.org (Postfix, from userid 1001) id C1AF06D455; Sun, 16 Nov 2003 07:00:57 -0600 (CST) Date: Sun, 16 Nov 2003 07:00:57 -0600 From: "Jacques A. Vidrine" To: Bruce Evans , Terry Lambert , freebsd-arch@FreeBSD.org Message-ID: <20031116130057.GA56160@madman.celabo.org> Mail-Followup-To: "Jacques A. Vidrine" , Bruce Evans , Terry Lambert , freebsd-arch@FreeBSD.org References: <20031114194119.GA94198@madman.celabo.org> <3FB6AA8F.37ED6D50@mindspring.com> <20031116102010.GA53282@madman.celabo.org> <20031116111212.GA55844@madman.celabo.org> <20031116231838.X1400@gamplex.bde.org> <20031116125230.GA56115@madman.celabo.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031116125230.GA56115@madman.celabo.org> X-Url: http://www.celabo.org/ User-Agent: Mutt/1.5.4i-ja.1 Subject: Re: __TIME_MIN/__TIME_MAX X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Nov 2003 13:01:00 -0000 On Sun, Nov 16, 2003 at 06:52:30AM -0600, Jacques A. Vidrine wrote: > On Sun, Nov 16, 2003 at 11:36:41PM +1100, Bruce Evans wrote: > > Actually, it's implementation-defined if time_t is integral (doesn't > > matter if it is signed or unsigned) (and the value is not representable). > > It's only undefined if time_t is a floating type. > > Are you certain? I'll have to double-check. I thought that if a type > was signed, then attempting to assign an out-of-range value was > undefined (similar to overflow with signed types). I should know better than to question whether you are certain :-) I think I have failed to differentiate between `implementation-defined' and `undefined'. I'd like to avoid both `implementation-defined' and `undefined' behavior. Cheers, -- Jacques Vidrine NTT/Verio SME FreeBSD UNIX Heimdal nectar@celabo.org jvidrine@verio.net nectar@freebsd.org nectar@kth.se From owner-freebsd-arch@FreeBSD.ORG Wed Nov 19 09:44:54 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 42B0A16A4CE for ; Wed, 19 Nov 2003 09:44:54 -0800 (PST) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 90C9443FAF for ; Wed, 19 Nov 2003 09:44:53 -0800 (PST) (envelope-from sam@errno.com) Received: from 66.127.85.91 ([66.127.85.91]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.9) with ESMTP id hAJHiqHQ034775 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Wed, 19 Nov 2003 09:44:53 -0800 (PST) (envelope-from sam@errno.com) From: Sam Leffler Organization: Errno Consulting To: freebsd-arch@freebsd.org Date: Wed, 19 Nov 2003 09:47:15 -0800 User-Agent: KMail/1.5.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200311190947.15416.sam@errno.com> Subject: adding crypto support to GENERIC X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Nov 2003 17:44:54 -0000 I'd like to add the in-kernel crypto support to the GENERIC kernel together with the hifn and ubsec drivers (not sure about the SafeNet driver as those cards are not often encountered). Doing this would enable out-of-the-box h/w accelerated openssl on machines with h/w crypto devices. This change would not affect the kernel on the floppy. This would be for the 5.2 release. Comments? Sam From owner-freebsd-arch@FreeBSD.ORG Wed Nov 19 09:51:14 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E48616A4CE for ; Wed, 19 Nov 2003 09:51:14 -0800 (PST) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id A67FA43FA3 for ; Wed, 19 Nov 2003 09:51:13 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) hAJHp58u016530; Wed, 19 Nov 2003 09:51:05 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)hAJHp5Q2016529; Wed, 19 Nov 2003 09:51:05 -0800 (PST) (envelope-from sgk) Date: Wed, 19 Nov 2003 09:51:05 -0800 From: Steve Kargl To: Sam Leffler Message-ID: <20031119175105.GA16518@troutmask.apl.washington.edu> References: <200311190947.15416.sam@errno.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200311190947.15416.sam@errno.com> User-Agent: Mutt/1.4.1i cc: freebsd-arch@freebsd.org Subject: Re: adding crypto support to GENERIC X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Nov 2003 17:51:14 -0000 On Wed, Nov 19, 2003 at 09:47:15AM -0800, Sam Leffler wrote: > I'd like to add the in-kernel crypto support to the GENERIC kernel together > with the hifn and ubsec drivers (not sure about the SafeNet driver as those > cards are not often encountered). Doing this would enable out-of-the-box h/w > accelerated openssl on machines with h/w crypto devices. This change would > not affect the kernel on the floppy. This would be for the 5.2 release. > > Comments? > What are the implications for individuals who live in countries that restrict access to crypto? -- Steve From owner-freebsd-arch@FreeBSD.ORG Wed Nov 19 10:08:53 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1009E16A4CE for ; Wed, 19 Nov 2003 10:08:53 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C5C143FE3 for ; Wed, 19 Nov 2003 10:08:51 -0800 (PST) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.10/8.12.10) with ESMTP id hAJI8cEs065829; Wed, 19 Nov 2003 19:08:39 +0100 (CET) (envelope-from phk@phk.freebsd.dk) To: Steve Kargl From: "Poul-Henning Kamp" In-Reply-To: Your message of "Wed, 19 Nov 2003 09:51:05 PST." <20031119175105.GA16518@troutmask.apl.washington.edu> Date: Wed, 19 Nov 2003 19:08:38 +0100 Message-ID: <65828.1069265318@critter.freebsd.dk> cc: Sam Leffler cc: freebsd-arch@freebsd.org Subject: Re: adding crypto support to GENERIC X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Nov 2003 18:08:53 -0000 In message <20031119175105.GA16518@troutmask.apl.washington.edu>, Steve Kargl w rites: >On Wed, Nov 19, 2003 at 09:47:15AM -0800, Sam Leffler wrote: >> I'd like to add the in-kernel crypto support to the GENERIC kernel together >> with the hifn and ubsec drivers (not sure about the SafeNet driver as those >> cards are not often encountered). Doing this would enable out-of-the-box h/w >> accelerated openssl on machines with h/w crypto devices. This change would >> not affect the kernel on the floppy. This would be for the 5.2 release. >> >> Comments? >> > >What are the implications for individuals >who live in countries that restrict access >to crypto? Are there any of those left ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-arch@FreeBSD.ORG Wed Nov 19 10:25:10 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B94316A4CE for ; Wed, 19 Nov 2003 10:25:10 -0800 (PST) Received: from smtpzilla5.xs4all.nl (smtpzilla5.xs4all.nl [194.109.127.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8015443FE3 for ; Wed, 19 Nov 2003 10:25:06 -0800 (PST) (envelope-from wkb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtpzilla5.xs4all.nl (8.12.9/8.12.9) with ESMTP id hAJIOw5a052979; Wed, 19 Nov 2003 19:24:59 +0100 (CET) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.12.9p2/8.12.9) with ESMTP id hAJIOwJM004719; Wed, 19 Nov 2003 19:24:58 +0100 (CET) (envelope-from wkb@freebie.xs4all.nl) Received: (from wkb@localhost) by freebie.xs4all.nl (8.12.9p2/8.12.9/Submit) id hAJIOwgY004718; Wed, 19 Nov 2003 19:24:58 +0100 (CET) (envelope-from wkb) Date: Wed, 19 Nov 2003 19:24:58 +0100 From: Wilko Bulte To: Poul-Henning Kamp Message-ID: <20031119182458.GA4703@freebie.xs4all.nl> References: <20031119175105.GA16518@troutmask.apl.washington.edu> <65828.1069265318@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <65828.1069265318@critter.freebsd.dk> User-Agent: Mutt/1.4.1i X-OS: FreeBSD 4.9-STABLE X-PGP: finger wilko@freebsd.org cc: Sam Leffler cc: Steve Kargl cc: freebsd-arch@FreeBSD.ORG Subject: Re: adding crypto support to GENERIC X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Nov 2003 18:25:10 -0000 On Wed, Nov 19, 2003 at 07:08:38PM +0100, Poul-Henning Kamp wrote: > In message <20031119175105.GA16518@troutmask.apl.washington.edu>, Steve Kargl w > rites: > >On Wed, Nov 19, 2003 at 09:47:15AM -0800, Sam Leffler wrote: > >> I'd like to add the in-kernel crypto support to the GENERIC kernel together > >> with the hifn and ubsec drivers (not sure about the SafeNet driver as those > >> cards are not often encountered). Doing this would enable out-of-the-box h/w > >> accelerated openssl on machines with h/w crypto devices. This change would > >> not affect the kernel on the floppy. This would be for the 5.2 release. > >> > >> Comments? > >> > > > >What are the implications for individuals > >who live in countries that restrict access > >to crypto? > > Are there any of those left ? France? -- | / o / /_ _ |/|/ / / /( (_) Bulte wilko@FreeBSD.org From owner-freebsd-arch@FreeBSD.ORG Wed Nov 19 10:52:31 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E92C816A4CE for ; Wed, 19 Nov 2003 10:52:31 -0800 (PST) Received: from math.teaser.net (math.teaser.net [213.91.2.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id C925843F75 for ; Wed, 19 Nov 2003 10:52:30 -0800 (PST) (envelope-from e-masson@kisoft-services.com) Received: from t39bsdems.interne.kisoft-services.com (nantes.kisoft-services.com [193.56.60.243]) by math.teaser.net (Postfix) with ESMTP id 3EB1B6C8D5; Wed, 19 Nov 2003 19:52:29 +0100 (CET) Received: by t39bsdems.interne.kisoft-services.com (Postfix, from userid 1001) id BF8C15B18A; Wed, 19 Nov 2003 19:52:18 +0100 (CET) To: Wilko Bulte From: Eric Masson In-Reply-To: <20031119182458.GA4703@freebie.xs4all.nl> (Wilko Bulte's message of "Wed, 19 Nov 2003 19:24:58 +0100") References: <20031119175105.GA16518@troutmask.apl.washington.edu> <65828.1069265318@critter.freebsd.dk> <20031119182458.GA4703@freebie.xs4all.nl> X-Operating-System: FreeBSD 4.9-STABLE i386 Date: Wed, 19 Nov 2003 19:52:18 +0100 Message-ID: <86ekw4nqcd.fsf@t39bsdems.interne.kisoft-services.com> User-Agent: Gnus/5.1003 (Gnus v5.10.3) XEmacs/21.4 (Portable Code, berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit cc: Sam Leffler cc: Poul-Henning Kamp cc: Steve Kargl cc: freebsd-arch@FreeBSD.ORG Subject: Re: adding crypto support to GENERIC X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Nov 2003 18:52:32 -0000 >>>>> "Wilko" == Wilko Bulte writes: >> Are there any of those left ? Wilko> France ? Use of cryptographic devices seems to spread quickly these days in France, Laws have been seriously softened in this area, but I don't know for sure actual status. I'll check on a french security dedicated group. Eric Masson -- Attends, s'il y a une toulousaine tu es gentil mais j'ai demandé le premier je crois. Premier arrivé premier servi quoi :-))))))))))) -+- GA in Guide du beauf primaire - "Envoyez la marchandise, VITE !"-+- From owner-freebsd-arch@FreeBSD.ORG Wed Nov 19 11:36:49 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB55016A4CE for ; Wed, 19 Nov 2003 11:36:49 -0800 (PST) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id D6FAD43F3F for ; Wed, 19 Nov 2003 11:36:48 -0800 (PST) (envelope-from sam@errno.com) Received: from 66.127.85.91 ([66.127.85.91]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.9) with ESMTP id hAJJalHQ035290 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Wed, 19 Nov 2003 11:36:48 -0800 (PST) (envelope-from sam@errno.com) From: Sam Leffler Organization: Errno Consulting To: Steve Kargl Date: Wed, 19 Nov 2003 11:39:10 -0800 User-Agent: KMail/1.5.3 References: <200311190947.15416.sam@errno.com> <20031119175105.GA16518@troutmask.apl.washington.edu> In-Reply-To: <20031119175105.GA16518@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200311191139.10420.sam@errno.com> cc: freebsd-arch@freebsd.org Subject: Re: adding crypto support to GENERIC X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Nov 2003 19:36:49 -0000 On Wednesday 19 November 2003 09:51 am, Steve Kargl wrote: > On Wed, Nov 19, 2003 at 09:47:15AM -0800, Sam Leffler wrote: > > I'd like to add the in-kernel crypto support to the GENERIC kernel > > together with the hifn and ubsec drivers (not sure about the SafeNet > > driver as those cards are not often encountered). Doing this would > > enable out-of-the-box h/w accelerated openssl on machines with h/w crypto > > devices. This change would not affect the kernel on the floppy. This > > would be for the 5.2 release. > > > > Comments? > > What are the implications for individuals > who live in countries that restrict access > to crypto? FWIW openbsd has shipped like this for a while and netbsd just switched over (but haven't shipped a system yet). I think it's time for us to do this too as h/w crypto support is becoming more common. Sam From owner-freebsd-arch@FreeBSD.ORG Wed Nov 19 15:49:59 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 33CDA16A4CE for ; Wed, 19 Nov 2003 15:49:59 -0800 (PST) Received: from cultdeadsheep.org (charon.cultdeadsheep.org [80.65.226.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4AF7343FE3 for ; Wed, 19 Nov 2003 15:49:54 -0800 (PST) (envelope-from sheepkiller@cultdeadsheep.org) Received: (qmail 48088 invoked by uid 85); 20 Nov 2003 00:49:51 +0100 Received: from sheepkiller@cultdeadsheep.org by goofy.cultdeadsheep.org by uid 82 with qmail-scanner-1.20rc2 ( Clear:RC:1:. Processed in 0.385471 secs); 19 Nov 2003 23:49:51 -0000 Received: from persephone.cultdeadsheep.org (192.168.0.8) by goofy.cultdeadsheep.org with SMTP; 20 Nov 2003 00:49:47 +0100 Received: (qmail 71853 invoked from network); 20 Nov 2003 00:50:26 +0100 Received: from unknown (HELO lucifer.cultdeadsheep.org) (192.168.0.2) by persephone.cultdeadsheep.org with DES-CBC3-SHA encrypted SMTP; 20 Nov 2003 00:50:26 +0100 Date: Thu, 20 Nov 2003 00:49:10 +0100 From: Clement Laforet To: Eric Masson Message-Id: <20031120004910.47a9d96d.sheepkiller@cultdeadsheep.org> In-Reply-To: <86ekw4nqcd.fsf@t39bsdems.interne.kisoft-services.com> References: <20031119175105.GA16518@troutmask.apl.washington.edu> <65828.1069265318@critter.freebsd.dk> <20031119182458.GA4703@freebie.xs4all.nl> <86ekw4nqcd.fsf@t39bsdems.interne.kisoft-services.com> Organization: tH3 cUlt 0f tH3 d3@d sH33p X-Mailer: Sylpheed version 0.9.7 (GTK+ 1.2.10; i386-portbld-freebsd5.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: sam@errno.com cc: phk@phk.freebsd.dk cc: freebsd-arch@FreeBSD.ORG cc: sgk@troutmask.apl.washington.edu cc: wkb@freebie.xs4all.nl Subject: Re: adding crypto support to GENERIC X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Nov 2003 23:49:59 -0000 On Wed, 19 Nov 2003 19:52:18 +0100 Eric Masson wrote: > >>>>> "Wilko" == Wilko Bulte writes: > > >> Are there any of those left ? > Wilko> France ? > > Use of cryptographic devices seems to spread quickly these days in > France, Laws have been seriously softened in this area, but I don't > know for sure actual status. If my memory serves me right, you can't use a key stronger than 128 bits except for software and uses authorized by the DCSSI. OpenSSL and GnuPG are authorized (thanks to France FSF): OpenSSL > 0.9.6d => SSH, SSL, SSH/SSL encryption GunPG > 1.0.7 => file/communication signature and encryption Are exempt from authorization: - Customised smart cards - Television reception equipment for the general public - Hardware or software means specially designed to protect software against copies or illegal use - cryptology equipment used in bank transactions - Portable or mobile radio telephones for civil applications - Cell phone radiocommunication base stations - Cryptology equipment accompanying foreign dignitaries when officially invited by the State. French: http://www.ssi.gouv.fr/fr/reglementation/regl_crypto.html http://www.ssi.gouv.fr/fr/reglementation/liste_entr/f28.html http://www.ssi.gouv.fr/fr/ English: http://www.ssi.gouv.fr/en/regulation/regl_crypto.html http://www.ssi.gouv.fr/en/ German: http://www.ssi.gouv.fr/de/regelung/regl_crypto.html http://www.ssi.gouv.fr/de/ clem From owner-freebsd-arch@FreeBSD.ORG Thu Nov 20 08:10:41 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9A9416A4CF for ; Thu, 20 Nov 2003 08:10:41 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0283544011 for ; Thu, 20 Nov 2003 08:10:34 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.9p2/8.12.9) with ESMTP id hAKG8DMg020760; Thu, 20 Nov 2003 11:08:13 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)hAKG88ut020757; Thu, 20 Nov 2003 11:08:08 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Thu, 20 Nov 2003 11:08:08 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Eric Masson In-Reply-To: <86ekw4nqcd.fsf@t39bsdems.interne.kisoft-services.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Sam Leffler cc: Poul-Henning Kamp cc: freebsd-arch@FreeBSD.ORG cc: Steve Kargl cc: Wilko Bulte Subject: Re: adding crypto support to GENERIC X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Nov 2003 16:10:41 -0000 On Wed, 19 Nov 2003, Eric Masson wrote: > >>>>> "Wilko" == Wilko Bulte writes: > > >> Are there any of those left ? > Wilko> France ? > > Use of cryptographic devices seems to spread quickly these days in > France, Laws have been seriously softened in this area, but I don't know > for sure actual status. > > I'll check on a french security dedicated group. Regardless, would the prohibition be on possession of the drivers for crypto hardware, or on possession and/or use of the crypto hardware? (In the US, export or even use of algorithm-independent crypto interfaces has been covered by export restrictions in the past, FYI). The hardware device drivers contain no crypto themselves, they just make use of hardware that's there. I would have thought the software algorithm implementations would be much more of an issue... Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories From owner-freebsd-arch@FreeBSD.ORG Fri Nov 21 01:27:45 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 822E716A4CE; Fri, 21 Nov 2003 01:27:45 -0800 (PST) Received: from eth0.b.smtp.sonic.net (eth0.b.smtp.sonic.net [64.142.19.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id B520543FE3; Fri, 21 Nov 2003 01:27:44 -0800 (PST) (envelope-from gharris@sonic.net) Received: from quadrajet.sonic.net (adsl-209-204-185-249.sonic.net [209.204.185.249])hAL9Rgni008972; Fri, 21 Nov 2003 01:27:43 -0800 Received: (from guy@localhost) by quadrajet.sonic.net (8.9.3/8.9.3) id BAA52399; Fri, 21 Nov 2003 01:27:41 -0800 (PST) (envelope-from gharris) Date: Fri, 21 Nov 2003 01:27:41 -0800 From: Guy Harris To: Bruce Evans Message-ID: <20031121012741.G329@quadrajet.sonic.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i cc: arch@FreeBSD.org cc: fenner@FreeBSD.org Subject: Re: bpf/pcap are weird X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Nov 2003 09:27:45 -0000 > > bpfpoll() is reported to be broken; see PR 36219. > > Yes, that's the PR that indicated that "select()"/"poll()" don't, in > fact, work correctly with timeouts. > > That was fixed in 4.5... > > > Rev.1.113 of bpf.c may have disturbed this. > > ...but might have been re-broken. > > > It removed the comment which said that > > bpf_ready() doesn't acually imitate resultof(FIONREAD) != 0. > > ...and it also removed the check for "d->bd_state == BPF_TIMED_OUT" that > made "select()"/"poll()" work with timeouts. I didn't read the code fully - no, it didn't. Revision 1.113 changed if (events & (POLLIN | POLLRDNORM)) { /* * An imitation of the FIONREAD ioctl code. * XXX not quite. An exact imitation: * if (d->b_slen != 0 || * (d->bd_hbuf != NULL && d->bd_hlen != 0) */ if (d->bd_hlen != 0 || ((d->bd_immediate || d->bd_state == BPF_TIMED_OUT) && d->bd_slen != 0)) revents |= events & (POLLIN | POLLRDNORM); else { selrecord(td, &d->bd_sel); /* Start the read timeout if necessary. */ if (d->bd_rtout > 0 && d->bd_state == BPF_IDLE) { callout_reset(&d->bd_callout, d->bd_rtout, bpf_timed_out, d); d->bd_state = BPF_WAITING; } } } to if (events & (POLLIN | POLLRDNORM)) { if (bpf_ready(d)) revents |= events & (POLLIN | POLLRDNORM); else { selrecord(td, &d->bd_sel); /* Start the read timeout if necessary. */ if (d->bd_rtout > 0 && d->bd_state == BPF_IDLE) { callout_reset(&d->bd_callout, d->bd_rtout, bpf_timed_out, d); d->bd_state = BPF_WAITING; } } } but revision 1.23 of "bpfdesc.h" introduce a macro "bpf_ready(bd)" that does #define bpf_ready(bd) \ ((bd)->bd_hlen != 0 || \ (((bd)->bd_immediate || (bd)->bd_state == BPF_TIMED_OUT) && \ (bd)->bd_slen != 0)) so the actual "bpf_poll()" code doesn't change. Revision 1.23 was MFC'ed to the 4.x branch in revision 1.14.2.3, which is in 4.9. (Also, the problem I mentioned with FreeBSD 4.4 not supporting the workaround for "select()" not working is in FreeBSD 4.3 as well.) From owner-freebsd-arch@FreeBSD.ORG Fri Nov 21 02:22:24 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC8F216A4CE for ; Fri, 21 Nov 2003 02:22:24 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E8E043FB1 for ; Fri, 21 Nov 2003 02:22:21 -0800 (PST) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.10/8.12.10) with ESMTP id hALALsmV004096; Fri, 21 Nov 2003 11:22:00 +0100 (CET) (envelope-from phk@phk.freebsd.dk) To: Clement Laforet From: "Poul-Henning Kamp" In-Reply-To: Your message of "Thu, 20 Nov 2003 00:49:10 +0100." <20031120004910.47a9d96d.sheepkiller@cultdeadsheep.org> Date: Fri, 21 Nov 2003 11:21:54 +0100 Message-ID: <4095.1069410114@critter.freebsd.dk> cc: freebsd-arch@FreeBSD.ORG cc: sgk@troutmask.apl.washington.edu cc: sam@errno.com cc: wkb@freebie.xs4all.nl Subject: Re: adding crypto support to GENERIC X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Nov 2003 10:22:25 -0000 In message <20031120004910.47a9d96d.sheepkiller@cultdeadsheep.org>, Clement Laf oret writes: >On Wed, 19 Nov 2003 19:52:18 +0100 >Eric Masson wrote: > >> >>>>> "Wilko" == Wilko Bulte writes: >> >> >> Are there any of those left ? >> Wilko> France ? >> >> Use of cryptographic devices seems to spread quickly these days in >> France, Laws have been seriously softened in this area, but I don't >> know for sure actual status. > >If my memory serves me right, you can't use a key stronger than 128 bits >except for software and uses authorized by the DCSSI. OpenSSL and GnuPG are >authorized (thanks to France FSF): Hang on here. We are not _forcing_ people to use the code, we are merely shipping it. I think we can conclude that no relevant country at this time restricts _possesion_ of crypto code, and that there is no problem in shipping it in GENERIC. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-arch@FreeBSD.ORG Fri Nov 21 02:29:07 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B952916A4CE for ; Fri, 21 Nov 2003 02:29:07 -0800 (PST) Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18C4A43FCB for ; Fri, 21 Nov 2003 02:29:06 -0800 (PST) (envelope-from sheldonh@starjuice.net) Received: from sheldonh by axl.seasidesoftware.co.za with local (Exim 4.24; FreeBSD) id 1AN8UU-0005i1-UP; Fri, 21 Nov 2003 12:26:18 +0200 Date: Fri, 21 Nov 2003 12:26:18 +0200 From: Sheldon Hearn To: Poul-Henning Kamp Message-ID: <20031121102618.GF18581@starjuice.net> Mail-Followup-To: Poul-Henning Kamp , Clement Laforet , freebsd-arch@FreeBSD.ORG, sgk@troutmask.apl.washington.edu, sam@errno.com, wkb@freebie.xs4all.nl References: <20031120004910.47a9d96d.sheepkiller@cultdeadsheep.org> <4095.1069410114@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4095.1069410114@critter.freebsd.dk> User-Agent: Mutt/1.5.4i cc: sam@errno.com cc: Clement Laforet cc: wkb@freebie.xs4all.nl cc: sgk@troutmask.apl.washington.edu cc: freebsd-arch@FreeBSD.ORG Subject: Re: adding crypto support to GENERIC X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Nov 2003 10:29:07 -0000 On (2003/11/21 11:21), Poul-Henning Kamp wrote: > Hang on here. We are not _forcing_ people to use the code, we are > merely shipping it. > > I think we can conclude that no relevant country at this time restricts > _possesion_ of crypto code, and that there is no problem in shipping > it in GENERIC. And the last time we took a ride on this merry-go-round, we concluded that we weren't interested in countries where possession of crypto code is illegal. Deja vu? :-) Ciao, Sheldon. From owner-freebsd-arch@FreeBSD.ORG Fri Nov 21 10:11:03 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 94EBA16A4CE for ; Fri, 21 Nov 2003 10:11:03 -0800 (PST) Received: from hanoi.cronyx.ru (hanoi.cronyx.ru [144.206.181.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7A6043F75 for ; Fri, 21 Nov 2003 10:10:59 -0800 (PST) (envelope-from rik@cronyx.ru) Received: (from root@localhost) by hanoi.cronyx.ru id hALI8IUn044268 for freebsd-arch@freebsd.org.checked; (8.12.8/vak/2.1) Fri, 21 Nov 2003 21:08:18 +0300 (MSK) (envelope-from rik@cronyx.ru) Received: from cronyx.ru (hi.cronyx.ru [144.206.181.94]) by hanoi.cronyx.ru with ESMTP id hALI6DY9044181; (8.12.8/vak/2.1) Fri, 21 Nov 2003 21:06:13 +0300 (MSK) (envelope-from rik@cronyx.ru) Message-ID: <3FBE54D0.9000901@cronyx.ru> Date: Fri, 21 Nov 2003 21:09:20 +0300 From: Roman Kurakin User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030401 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-arch@freebsd.org, freebsd-current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: MAJOR number X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Nov 2003 18:11:03 -0000 Hi, I need a new MAJOR number for our new device. How can I get it? I've read that FreeBSD doesn't use them any more. But we may need it to not interfere with other device drivers in previous releases of FreeBSD. ??? ce Cronyx Tau-32 E1 adapter ___ Best regars, Roman Kurakin Cronyx Engineering http://www.cronyx.ru From owner-freebsd-arch@FreeBSD.ORG Fri Nov 21 12:28:26 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B3E0A16A4CE; Fri, 21 Nov 2003 12:28:26 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7821343F75; Fri, 21 Nov 2003 12:28:25 -0800 (PST) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.9p2/8.12.9) with ESMTP id hALKSAeG008103; Fri, 21 Nov 2003 13:28:10 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Fri, 21 Nov 2003 13:27:49 -0700 (MST) Message-Id: <20031121.132749.91314507.imp@bsdimp.com> To: rik@cronyx.ru From: "M. Warner Losh" In-Reply-To: <3FBE54D0.9000901@cronyx.ru> References: <3FBE54D0.9000901@cronyx.ru> X-Mailer: Mew version 2.1 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: freebsd-arch@freebsd.org Subject: Re: MAJOR number X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Nov 2003 20:28:26 -0000 In message: <3FBE54D0.9000901@cronyx.ru> Roman Kurakin writes: : ??? ce Cronyx Tau-32 E1 adapter I've checked -stable and -current. You may have: 185 ce Cronyx Tau-32 E1 adapeter for your adapter. Sorry for the hassles in getting it. I'll be checking in this shortly, but we're in a freeze right now so it may take a little while. Warner From owner-freebsd-arch@FreeBSD.ORG Sat Nov 22 06:07:57 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B3FE016A4F1 for ; Sat, 22 Nov 2003 06:07:57 -0800 (PST) Received: from hanoi.cronyx.ru (hanoi.cronyx.ru [144.206.181.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 302BE43F3F for ; Sat, 22 Nov 2003 06:07:56 -0800 (PST) (envelope-from rik@cronyx.ru) Received: (from root@localhost) by hanoi.cronyx.ru id hAME5Cod029372 for freebsd-arch@freebsd.org.checked; (8.12.8/vak/2.1) Sat, 22 Nov 2003 17:05:12 +0300 (MSK) (envelope-from rik@cronyx.ru) Received: from cronyx.ru (hi.cronyx.ru [144.206.181.94]) by hanoi.cronyx.ru with ESMTP id hAME4u9q029346; (8.12.8/vak/2.1) Sat, 22 Nov 2003 17:04:56 +0300 (MSK) (envelope-from rik@cronyx.ru) Message-ID: <3FBF6DC0.6050802@cronyx.ru> Date: Sat, 22 Nov 2003 17:08:00 +0300 From: Roman Kurakin User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030401 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "M. Warner Losh" References: <3FBE54D0.9000901@cronyx.ru> <20031121.132749.91314507.imp@bsdimp.com> In-Reply-To: <20031121.132749.91314507.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: freebsd-arch@freebsd.org Subject: Re: MAJOR number X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Nov 2003 14:07:57 -0000 Thanks! Best regards, Roman Kurakin M. Warner Losh wrote: >In message: <3FBE54D0.9000901@cronyx.ru> > Roman Kurakin writes: >: ??? ce Cronyx Tau-32 E1 adapter > >I've checked -stable and -current. You may have: > >185 ce Cronyx Tau-32 E1 adapeter > >for your adapter. Sorry for the hassles in getting it. I'll be >checking in this shortly, but we're in a freeze right now so it may >take a little while. > >Warner > > > >