compressed,
that a "one size fits all" compression method inside SSL wasn't going to
give worthwhile benefits for all data,
and that it is best done at application layer rather than in the network.
the paper is at
http://www.rsasecurity.com.au/rsa99/ssl-tls.pdf
regards,
/Nei
((unsigned char *)ci,sizeof(ci));
GetCursorPos(pt);
RAND_seed((unsigned char *)pt,sizeof(pt));
Sleep(1000);
//rand_cb(gCtx);
}
return 0; // unreachable. but the fuction should have a return value !
}
Regards
Neil C
Richard,
on the 2 reports
(as it looks like you don't have a win32 installation)
i can confirm the modifications seem to work
1. i manually copied the md32_common.h to inc32 and the build proceeded
to the next problem
2. i commented out the #ifdef __MINGW32__..#endif in the e_os.h
and it
.pdf
/neil
begin:vcard
n:;Neil Costigan
tel;work:650 938 7600 x 204
x-mozilla-html:FALSE
url:http://www.celocom.com
org:Celo Communications Inc.
adr:;;444 Castro Street, Suite 1001;Mountain View;California;94041;USA
version:2.1
email;internet:[EMAIL PROTECTED]
note;quoted-printable:Alternative
Stephen,
did i ever send you a copy of this ssl-c thing ?
/neil
begin:vcard
n:Costigan;Neil
tel;cell:US: 650 .787.7603 Europe: +46.708.977.482
tel;work:US: 650-938-7600 Europe: +46.8.587 288 00
x-mozilla-html:TRUE
url:http://www.celocom.com
org:A HREF="http://www.celocom.com"Celo
Jon Parry-McCulloch wrote:
Greetings,
My company has just bought RSA BSAFE SSL C for me to use in the
exported-to-the-US versions of the product we're developing.
Two things:
a) anyone know if this is call-for-call compatible with SSLeay 0.9b
not
