1996-06-03 - Re: Java Crypto API questions

Header Data

From: Jeff Weinstein <jsw@netscape.com>
To: Andrew Loewenstern <andrew_loewenstern@il.us.swissbank.com>
Message Hash: bcc43f33a9b6aeee3110fca4b1b0082329ed1b459e6d98fe6f2cc98f9cb7b821
Message ID: <31B2ADA5.577D@netscape.com>
Reply To: <Pine.SUN.3.91.960531114414.23205A-100000@rwd.goucher.edu>
UTC Datetime: 1996-06-03 13:09:04 UTC
Raw Date: Mon, 3 Jun 1996 21:09:04 +0800

Raw message

From: Jeff Weinstein <jsw@netscape.com>
Date: Mon, 3 Jun 1996 21:09:04 +0800
To: Andrew Loewenstern <andrew_loewenstern@il.us.swissbank.com>
Subject: Re: Java Crypto API questions
In-Reply-To: <Pine.SUN.3.91.960531114414.23205A-100000@rwd.goucher.edu>
Message-ID: <31B2ADA5.577D@netscape.com>
MIME-Version: 1.0
Content-Type: text/plain


Andrew Loewenstern wrote:
> 
> Moltar Ramone writes:
> >  Probably.  But they won't be able to export the signed 3DES
> >  package :) It leaves foreign vendors in trouble, is where.
> 
> Sun can export the signature though.  The vendor already has the package,
> they just need the sig/cert...

  Not likely.  Sun will probably be required to agree not to do this
as a condition of exporting software with "pluggable crypto".  Software
with hooks for crypto functions is treated the same as the actual crypto
as far as the ITAR is concerned.

	--Jeff

-- 
Jeff Weinstein - Electronic Munitions Specialist
Netscape Communication Corporation
jsw@netscape.com - http://home.netscape.com/people/jsw
Any opinions expressed above are mine.





Thread