[923] in arla-drinkers
Re: klog-clone
daemon@ATHENA.MIT.EDU (allbery@kf8nh.apk.net)
Mon Jun 28 19:05:31 1999
From owner-arla-drinkers@stacken.kth.se Mon Jun 28 23:05:28 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 17457 invoked from network); 28 Jun 1999 23:05:26 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 28 Jun 1999 23:05:26 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id AAA07309
for arla-drinkers-list; Tue, 29 Jun 1999 00:58:59 +0200 (MET DST)
Received: from ece.cmu.edu (ECE.CMU.EDU [128.2.236.200])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id AAA07305
for <arla-drinkers@stacken.kth.se>; Tue, 29 Jun 1999 00:58:55 +0200 (MET DST)
From: allbery@kf8nh.apk.net
Received: from hilfy.ece.cmu.edu (root@HILFY.ECE.CMU.EDU [128.2.236.133])
by ece.cmu.edu (8.9.2/8.8.8) with ESMTP id SAA05567;
Mon, 28 Jun 1999 18:58:52 -0400 (EDT)
Received: from speaker.kf8nh.apk.net (root@ANNEX-1.ECE.CMU.EDU [128.2.236.1])
by hilfy.ece.cmu.edu (8.9.2/8.8.8) with ESMTP id SAA15287;
Mon, 28 Jun 1999 18:58:51 -0400 (EDT)
Received: from kf8nh.apk.net (allbery@rushlight.kf8nh.apk.net [10.9.204.1])
by speaker.kf8nh.apk.net (8.8.7/8.8.7) with ESMTP id SAA01175;
Mon, 28 Jun 1999 18:58:44 -0400
Message-Id: <199906282258.SAA01175@speaker.kf8nh.apk.net>
Date: Mon, 28 Jun 1999 18:58:43 -0400 (EDT)
Reply-To: allbery@ece.cmu.edu
Subject: Re: klog-clone
To: shadow@dementia.org
cc: arla-drinkers@stacken.kth.se
In-Reply-To: <ML-1.3.2.930608824.1367.shadow@johnstown.andrew.cmu.edu>
MIME-Version: 1.0
Content-Type: TEXT/plain; CHARSET=US-ASCII
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
On 28 Jun, Derrick J Brashear wrote:
+-----
| > HOWEVER: for those outside the U.S., including Herbert, I suspect both
| > Derrick's and your archives aren't legally supposed to provide access
| > to those modules.
|
| Actually, given that they don't encrypt arbitrary end-user data, there's not
| really any reason why they would be not exportable
+--->8
Yeah, but the bloody U.S. regs cover anything with *hooks* into or for
encryption software as well. Which means that the State Department can
make it fit if they want to get nasty about it. **grrr**
--
brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net
system administrator [WAY too many hats] allbery@ece.cmu.edu
carnegie mellon / electrical and computer engineering KF8NH
We are Linux. Resistance is an indication that you missed the point.
