On Wed, 2 Jan 2002 22:53:50 -0600, Vincent Toms wrote:
>Hello All, I have a question about what ciphers to use in an export ready
>app.
>I then watch the connection and it picks one of these ciphers and conducts
>the interaction successfully. My question is do I need to do any more than
>use on
Hi,
I have a few questions about the usage of the PKCS7 functions in
OpenSSL.
My code works: it creates a PKCS7 SignedAndEnveloped. I get the idea
from the enc.c and dec.c files in crypto/pkcs7 directory.
Before my code worked i wrote another code that seemed to be ok bu
I was under the impression that we didnt need to use export ciphers
anymore? Could someone just glaze over this fact?
- Andrew
- Original Message -
From: "David Schwartz" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, January 03, 2002 3:58 AM
Subject: Re: Cipher question
The App itself is closed source but I use opensouce libs namely
OpenSSL and a popular image manipulation library. The client is
win32 and I am linking dynamicly. I just want it so that I can
release the app both here and abroad with out fear of encryption law
violations.
Thanks again.
Vincen
Andrew T. Finnell wrote:
> I was under the impression that we didnt need to use export ciphers
> anymore? Could someone just glaze over this fact?
>
There is no legal reason for US software to use export ciphers.
You might have to support old browsers or apps, however.
--
Zolera Systems,
On Mon, 31 Dec 2001, John E. Lopez wrote:
> I want to write a TCP(Watt-32 tcp/ip http://www.bgnett.no/~giva/) msdos
> application that uses openssl.
Openssl compiles with DJGPP just fine. It doesn't support the entropy
gathering daemon, so you have to make sure that your program supplies
a sour
Hi All
About a 15 months ago i asked if there were any
developers interested in creating a C++ wrapper class library using openssl
for NT non MFC and coexisting with IIS, STL and Sql Server. If Interested
please drop me a line
robert
In OpenSSL 0.9.6b, for both SunOS 4 and Solaris 2.6, I have noticed that
specifying gcc as the compiler is reflected in some of the Makefiles, but
not all: in some of subdirectories "CC" is left set to the default "cc".
I suspect this is really a problem with either the Configure script, or
with