Hi,
I'm finally catching up and updating our OPENSSL *.dll distribution
with the latest build (0.9.8i). We had 0.9.8a (2006 time frame)
The main reason is because we got inquiries regarding AES and SSL3 and
cipher suites.
I am trying to recall all our work, but I thought we had server
Folks,
I just got the 0.9.9dev SNAPSHOT (openssl-SNAP-20081227.tar.gz) and
for a WIN32 build, I got the build error:
perl crypto\camellia\asm\cmll-x86.pl win32n /MDd /Od -DDEBUG
-D_DEBUG -DOPENSSL_THREADS -DDSO_W
IN32 -W3 -WX -Gs0 -GF -Gy -nologo -DOPENSSL_SYSNAME_WIN32
Folks,
I can't help but notice that what happen to the PHP development team,
the Google Chrome development team, is now happening with the OPENSSL
development team.
That is, with Microsoft pushing out a freebie compiler VS2005 (VC8)
and now VS2008 (VC9), building developments that use to
Thanks Richard, Bill and et.
I didn't see a straight forward document saying if the prototypes or
structures changed in 0.9.8a, but part of the reason to do the update
(besides security issues) was that I am starting on a new project that
requires the EVP_SHA256 function and when I first compiled
I have multiple applications using OPENSSL 0.9.7c and I'm finally getting
around to updating it.
I have downloaded and recompiled the *eay*.dll files for:
0.9.7i
0.9.8a
Can I just use the new DLLs for 0.9.8a or do I need to recompile my
applications? I take it I will be fine with
I am relatively new to OPENSSL. I have implemented OPENSSL into our hosting
software and I'm writing a GUI certificate manager specific to my
application. I have a few questions:
1) Whats the point of the Request Attributes? In the OPENSSL.CNF file,
there is two attributes, challengePassword
