From: Jeff Barber <jeffb@sware.com>
To: droelke@rdxsunhost.aud.alcatel.com (Daniel R. Oelke)
Message Hash: 924d2c7965b524034d93eed9a124b7c8221336ae853c095df518e4058dc3fad6
Message ID: <199604102054.QAA23703@jafar.sware.com>
Reply To: <9604101921.AA25061@spirit.aud.alcatel.com>
UTC Datetime: 1996-04-11 04:50:01 UTC
Raw Date: Thu, 11 Apr 1996 12:50:01 +0800
From: Jeff Barber <jeffb@sware.com>
Date: Thu, 11 Apr 1996 12:50:01 +0800
To: droelke@rdxsunhost.aud.alcatel.com (Daniel R. Oelke)
Subject: Re: Bank information protected by 40-bit encryption....
In-Reply-To: <9604101921.AA25061@spirit.aud.alcatel.com>
Message-ID: <199604102054.QAA23703@jafar.sware.com>
MIME-Version: 1.0
Content-Type: text/plain
Daniel R. Oelke writes:
> If you are the worring sort (or are looking for a ripe target)
> point your browser at:
> https://www.diginsite.com/clients.html
>
> There is a list of 23 Credit Unions - some (or all) of which
> allow transactions to be done over the net.
>
> A brief once over shows that it requires Netscape 2.0 or
> better so you will have encryption, but it does not warn you
> when you are using only a 40-bit session key vs. a 128-bit key.
> (Netscape wizards - is there a way that the server can detect
> this so that a warning message could be put up?)
Yes. Netscape servers pass three (additional) environment variables to
CGI programs when used with SSL. For a 40-bit invocation, you get:
HTTPS=ON
HTTPS_KEYSIZE=128
HTTPS_SECRETKEYSIZE=40
So, you can distinguish 40- versus 128-bit usage.
-- Jeff
Return to April 1996
Return to “Tom Weinstein <tomw@netscape.com>”