From owner-freebsd-hackers@FreeBSD.ORG Wed Oct 22 14:46:58 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2A8E9773 for ; Wed, 22 Oct 2014 14:46:58 +0000 (UTC) Received: from mail-ob0-f180.google.com (mail-ob0-f180.google.com [209.85.214.180]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E476624D for ; Wed, 22 Oct 2014 14:46:57 +0000 (UTC) Received: by mail-ob0-f180.google.com with SMTP id vb8so646588obc.39 for ; Wed, 22 Oct 2014 07:46:56 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=n9rJZmEn5VZANA2wuptJ+wspmpEQNGVInGOGh4gqFrg=; b=V4oyJPevk3nh/EBeMRSAeyGBC01whPV+qI4h+WRLEMWyzI8GfqYIySGN9A5zLueSgs ffMMdLmQS43uI3Zv1FSpHyBqtTd2VeRpxeEeL6izc5TxZm3MavZ0scq2OuOLxNlCvWeJ yIS7C9Y2mwoc067uTD2pUHYvl+LbbW5mQUMvZRBCVN6YyEQGJPIYT9aT7QUaF+wJs9rS w6rD5ARosH8C3TqjpRxW60rNuJm9HmFtWSYbDELkSMjneRMHwMSusv9/RxMaG1j53YVV GSorc2QuItKFWp2prSsAEuX836yp/5hf3me+LUCWxjeNr+Iy3U2JgLIlD1t2zAUzGRVZ zAAg== X-Gm-Message-State: ALoCoQmuM9hhZ4H3evhUmgppwocbS2ThlNYHhHWnL4FkoJl6h/Xz5o0GZGrm7sOzdAi/mLEUulcW X-Received: by 10.60.147.196 with SMTP id tm4mr35879637oeb.4.1413989216234; Wed, 22 Oct 2014 07:46:56 -0700 (PDT) Received: from [172.21.0.83] (65-36-83-120.static.grandenetworks.net. [65.36.83.120]) by mx.google.com with ESMTPSA id cy12sm6320145oec.5.2014.10.22.07.46.55 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 22 Oct 2014 07:46:55 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: DOC obstructs encryption export again - Non USA crypto base again ? From: Jim Thompson X-Mailer: iPhone Mail (12B411) In-Reply-To: <201410221424.s9MEOWwT000965@fire.js.berklix.net> Date: Wed, 22 Oct 2014 09:46:55 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: References: <201410221424.s9MEOWwT000965@fire.js.berklix.net> To: "Julian H. Stacey" Cc: "freebsd-hackers@freebsd.org" , Poul-Henning Kamp X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Oct 2014 14:46:58 -0000 > As far as I have been able to uncover, this settlement is about a > commercial closed source component, using specific hardware-crypto-assist,= for which no programming details have been made publically available. I have strong reason to believe this was about Intel's EP89579 (Tolapai) "Qu= ickAssist" core.=20 In 2009 or 2010, FreeBSD was offered a driver, with attached source code, fr= om an Intel engineer in Ireland on one of our lists. Intel also had a NIC with the same core available during the period covered b= y the complaint against Wind River.=20 If it was QuickAssist, then said details are available for its descendants o= n 01.org, and in recent Linux trees.=20 jmg@, eri@ and a few others have been investigating a FreeBSD driver for sam= e.=20 At the end of the day, "nothing to see here, move along." Jim