Re: SNMPv2 security

Frank Kastenholz <kasten@tri-flow.ftp.com> Fri, 28 January 1994 22:58 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa14555; 28 Jan 94 17:58 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa14551; 28 Jan 94 17:58 EST
Received: from relay.tis.com by CNRI.Reston.VA.US id aa18755; 28 Jan 94 17:58 EST
Received: by relay.tis.com; id AA02088; Fri, 28 Jan 94 17:32:41 EST
Received: from magellan.tis.com(192.33.112.124) by relay via smap (V1.0mjr) id smad02064; Fri Jan 28 17:32:21 1994
Received: from magellan.tis.com by magellan.TIS.COM id aa17063; 28 Jan 94 17:27 EST
Received: from sol.tis.com by magellan.TIS.COM id aa17054; 28 Jan 94 17:22 EST
Received: from relay.tis.com by tis.com (4.1/SUN-5.64) id AA02367; Fri, 28 Jan 94 17:22:04 EST
Received: by relay.tis.com; id AA01924; Fri, 28 Jan 94 17:22:33 EST
Received: from babyoil.ftp.com(128.127.2.105) by relay via smap (V1.0mjr) id sma001918; Fri Jan 28 17:22:25 1994
Received: from tri-flow.ftp.com by babyoil.ftp.com with SMTP id AA09985; Fri, 28 Jan 94 17:22:15 -0500
Received: by tri-flow.ftp.com.ftp.com (5.0/SMI-SVR4) id AA05331; Fri, 28 Jan 94 17:22:12 EST
Date: Fri, 28 Jan 1994 17:22:12 -0500
Message-Id: <9401282222.AA05331@tri-flow.ftp.com.ftp.com>
To: adam@kbss.bt.co.uk
Subject: Re: SNMPv2 security
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Frank Kastenholz <kasten@tri-flow.ftp.com>
Reply-To: kasten@ftp.com
Cc: snmp@psi.com, snmpv2@magellan.tis.com
Content-Length: 2047

 > > The whole point of this exercise is to remove the mandated need for
 > > DES -- that is, to remove the Priv. The intent of this scheme is to
 > > provide a way to distribute and update Auth keys without requiring an
 > > encryption algorithm (like DES) which would run afoul of various
 > > export laws. In this context, your statement is a nonsense.
 > 
 > Given that the DES algorithms are now freely available to all outside
 > the states is this an issue anymore? Perhaps some european suppliers

As far as US law goes, the fact that DES software is available
outside the US is irrelevant. I believe that the DES specification
was available to anyone who asked.

Here's an example of how the legalistic/bureaucratic mind can work: 2
or three years ago, as Russia (it might have been the USSR then) was
trying to find commercial purchasers of some of the technology that
they developed for their space program, they brought a small nuclear
reactor to the US to show it off to some prospective customers. When
it came time for them to go back to Russia, they were stopped at our
(the US) border by our customs people who politely and firmly told
them that it was illegal to export the reactor. The Russians, and
high-level Americans, all protested that the reactor was made by the
Russians, in Russia and obviously represented technology that the
Russians had (since they made the silly thing). The customs people
listened very carefully and then said that it didn't matter where the
reactor was made or who made it, the law said "Thou Shalt Not Export
Reactors" and that was that -- and customs then impounded the
reactor. Eventually it took an act of Congress to make it legal to
export that specific reactor (Model such-and-such, color so-and-so,
size foo-by-bar, serial number mumble and so on) to its owners.

To apply this story to our situation, do a global search-and-replace
from "reactor" to "code containing cryptologic technology".


--
Frank Kastenholz
FTP Software
2 High Street
North Andover, Mass. USA 01845
(508)685-4000