On Wed, Jun 28, 2006, Dr. Stephen Henson wrote:
>
> It may be possible to adapt the new distribution to VC++ but I doubt it at
> this stage.
>
Update: I don't want to raise any false hopes so let me just very guardedly
say that things aren't looking as bad as they were a couple of hours ago.
On 6/28/06, Dr. Stephen Henson <[EMAIL PROTECTED]> wrote:
On Wed, Jun 28, 2006, Hagai Yaffe wrote:
> Is it possible that there will not be an OpenSSL FIPS validated version
> for Windows?
>
The MingW+MSYS build works fine on Windows so in that sense there will be a
"version for Windows". Howeve
On Wed, Jun 28, 2006, Hagai Yaffe wrote:
> Is it possible that there will not be an OpenSSL FIPS validated version
> for Windows?
>
The MingW+MSYS build works fine on Windows so in that sense there will be a
"version for Windows". However applications would have to be developed using
MingW.
T
sers@openssl.org
Subject: Re: Creating an Application according to the OpenSSL FIPS
Security Policy
On Tue, Jun 27, 2006, Hagai Yaffe wrote:
>
> I would then like to use that DLL from a few applications (by way of
> linking or dynamic loading), this DLL will provide all the
cryp
Is this causing crashes with statically-linked, dynamically-linked, or
both? (And what kinds of crashes? Knowing something about what's
going on could allow for the MingW environment to be tweaked, as long
as it's still compiling and linking in an appropriate fashion?)
Also, is any thought goin
On Tue, Jun 27, 2006, Hagai Yaffe wrote:
>
> I would then like to use that DLL from a few applications (by way of
> linking or dynamic loading), this DLL will provide all the cryptographic
> needs of the relevant applications. My question is if this way of use
> complies with the OpenSSL FIPS Sec
