Thread View: sci.crypt
3 messages
3 total messages
Started by William Hawkins
Mon, 21 Dec 1992 06:55
Re: Exporting password protection
Author: William Hawkins
Date: Mon, 21 Dec 1992 06:55
Date: Mon, 21 Dec 1992 06:55
47 lines
2764 bytes
2764 bytes
Thanks to you who have replied to my query on exporting password protection. You are correct that it is a matter for Commerce, and not State, but that is the problem. In July of '92, the Department of State, Bureau of Politico- Military Affairs, issued an amendment to the International Traffic in Arms Regulations Munitions List. Basically, it says that a company wishing to export a mass market software product containing encryption may apply to DOS (State) for a transfer of jurisdiction to the Department of Commerce (DOC) IF the software is mass market (over the counter with no special training or support (process control systems require lots of training and support, but not for encryption)) AND the data encryption algorithm is RC4 and/or RC2 with a key space of 40 bits. It is noted that RC4 and RC2 are proprietary to RSA Data Security, Inc. It must not be possible for both RC4 and RC2 to operate on the same data. If you can meet those criteria, you can be transferred to DOC in one to two weeks. The problem is that Commerce seems to think that anything that hides data requires an export license. Reading the words, it looks like rot13 would be prohibited without a license. Nor does it count that your non mass media software uses the *same* encryption algorithm as mass media software. One kind of DOC license requires the recipient of the software to swear that the software will not be exported to anyone on the restricted list. You can imagine how much trouble it must be to keep up with the list. Think about it. The list is made for geographical boundaries. When is the last time that a piece of geography threatened you? Iran is on the forbidden list. Are there any citizens of Iran outside the geographical borders of that country? Do they have access to encryption techniques? I do not mean to pick on Iran, but only to show that the borders have nothing to do with access to information. We will, of course, comply with the law of the land, as interpreted by the nearest bureaucrat. By way of disclaimer, it is not my job to find out what the bureaucracy requires; I only sit on the sidelines and watch it all go by. Today is the 21'st. News arrives from the 15'th, so I still invite email replies. bill@texan.rosemount.com Minneapolis, MN (612) 895-2085
Re: Exporting password protection
Author: Philip Gladstone
Date: Tue, 22 Dec 1992 03:02
Date: Tue, 22 Dec 1992 03:02
12 lines
859 bytes
859 bytes
bill@texan.rosemount.com (William Hawkins) writes: [stuff deleted] : the data : encryption algorithm is RC4 and/or RC2 with a key space of 40 : bits. It is noted that RC4 and RC2 are proprietary to RSA : Data Security, Inc. Is there a published description of these algorithms anywhere? If not, then does anyone know if software incorporating these algorithms has actually been exported out of the US? Philip
Re: Exporting password protection
Author: Phil Karn
Date: Tue, 22 Dec 1992 06:05
Date: Tue, 22 Dec 1992 06:05
12 lines
1122 bytes
1122 bytes
In article <1992Dec22.030202.13922@meiko.com> philip@meiko.com (Philip Gladstone) writes: >Is there a published description of these algorithms anywhere? (referring to RC2 and RC4) No, as far as I know. I read something from RSADSI a few weeks ago that says RC2 and RC4 are single-key ciphers proprietary to RSADSI, and that "to maintain their special export status" their designs will not be released. See if *you* can figure out what this means. Phil
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads