1998-05-13 - Chaffing and winnowing

Header Data

From: “Mark Rosen” <mrosen@peganet.com>
To: “Mordechai Ovits” <ryan@michonline.com>
Message Hash: 7c2beca8e9940a2212f21fe6aec7e46ac98d5867ffa0b71db1628dd9bec25bb7
Message ID: <01bd7e04$5802a820$014ce9c7@markdsk.peganet.com>
Reply To: N/A
UTC Datetime: 1998-05-13 00:21:50 UTC
Raw Date: Tue, 12 May 1998 17:21:50 -0700 (PDT)

Raw message

From: "Mark Rosen" <mrosen@peganet.com>
Date: Tue, 12 May 1998 17:21:50 -0700 (PDT)
To: "Mordechai Ovits" <ryan@michonline.com>
Subject: Chaffing and winnowing
Message-ID: <01bd7e04$5802a820$014ce9c7@markdsk.peganet.com>
MIME-Version: 1.0
Content-Type: text/plain

    I have just been notified that chaffing and winnowing does, indeed,
violate the export regulations. You can read them for yourself at
http://www.bxa.doc.gov/Encryption/encreg.htm, but here are a few parts

a. Designed or modified to use ``cryptography'' employing digital techniques
to ensure ``information security'';
b. Designed or modified to perform cryptanalytic functions;
c. Designed or modified to use ``cryptography'' employing analog techniques
to ensure ``information security'';
Note: 5A002 does not control the following:
b. Equipment containing ``fixed'' data compression or coding techniques;
g. Data authentication equipment that calculates a Message
Authentication Code (MAC) or similar result to ensure no alteration of
text has taken place, or to authenticate users, but does not allow for
encryption of data, text or other media other than that needed for the

    So it seems 5A002.a  and 5A002.g cover such encryption technologies as
chaffing and winnowing. Interestingly enough, 5A002.b allows such functions
as the package transform (keyless coding), even though it uses encryption

- Mark Rosen