-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Reddie, Steven
Sent: Sunday, February 25, 2001 4:26 PM
To: [EMAIL PROTECTED]
Subject: RE: Maximum size of RSA message, was: Re: RSA Encrypt/Decrypt
fails
The message being encrypted/decrypted MUST be smal
We have had success using the MS Internet Explorer core (WININET.DLL) to
create a WIN32 SSL client. There are a number of exposed API calls in
WININET which make this job pretty easy (some of which call other MS DLL's
which perform the cypto
I'm wondering if the Netscape environment has similar
John -- Take a look at the WININET.DLL resources on the MS site. This DLL
is the core of Internet Explorer and the API set is exposed to developers.
The user must have IE installed on their machine (although it needn't be
their default browser) for this to work.
HTH
Harry
-Original Message
Albert
How about using an HTTPS PUT operation?
Best
Harry
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Albert Serra
Sent: Tuesday, June 27, 2000 2:51 AM
To: [EMAIL PROTECTED]
Subject: string - file
Hello again,
another question,
if I want to tran
PMFJI...
How does one utilize something like a Cisco PIX firewall in an SSL
environment? On option the firewall seems to offer is translation of
network addresses, so a message that might be routed to vvv.xxx.yyy.zzz (a
web-registered address) could rerouted to a private network address by the
f
As I read the SSL3 specs, I gather that random bytes from the client
(generated as part of Client Hello) are combined with the client-generated
pre-master secret and random bytes from the server (generated at the Server
Hello) to yield the master secret.
I'm curious as to the rationale for using
Rene, Nicholas, Ben, Terrell and Goetz --
Thanks to your all for your comments! Most helpful!
Harry
__
OpenSSL Project http://www.openssl.org
User Support Mailing List[EMAI
This may be slightly off-topic, so let me apologize in advance.
The SSL protocol requires that the client side (say a browser) use
appropriate crypto to read the server's certificate and verify the signature
on the transmitted public key (using the public key of a trusted 3rd party
such as Verisi
9 9:07 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: OT: Hardware proxy?
At 02:47 PM 7/21/99 -0700, Harry Whitehouse wrote:
>
>Is there an industrial-strength proxy available commerically which only
>permits 443 traffic? I know I could get something like MS Proxy Server
>softw
PMFJI --
I'm curious as to what folks have used to separate the SSL server from the
"isolated back end". SCSI, RS232, other techniques? Are there commerical
solutions available?
TIA
Harry
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Craig Southere
10 matches
Mail list logo