On Sat, Oct 16, 2010, Grant Averett wrote:
Hello, I've successfully built the validated FIPS object module and OpenSSL
0.9.8o on Windows with Visual Studio 2008 many times (both an x86 and x64
version) without issue and I can successfully build both with Visual Studio
2010. However, the
The documentation still lists the 'openssl ts' command but I couldn't find
it in the source code anymore. I wanted to explore the features of OpenSSL
recently, so I developed a RFC 3161-conformant timestamp server using
OpenSSL based on the PKCS7 support. Some questions regading this:
1. After
Dr Henson:
I just built fips-1.2 under VS2010 (from a Visual Studio 2010 command prompt,
under Windows Server 2008 [not 2008R2]). Running out32dll\openssl.exe itself,
with environment OPENSSL_FIPS=1, returns:
C:\openssl-fips-1.2\openssl-fips-1.2\out32dllopenssl
5324:error:2D06906E:FIPS
Ugh. This is worse than I thought. It's *intermittently* failing like that.
After a few more minutes, I tried it again, and got the expected output.
Is there some way to specify a base address during the creation of the DLL,
after the fipscanister is created? Would that invalidate it?
The
On Sun, Oct 17, 2010, aerow...@gmail.com wrote:
Ugh. This is worse than I thought. It's *intermittently* failing like
that. After a few more minutes, I tried it again, and got the expected
output.
Is there some way to specify a base address during the creation of the DLL,
after the
On Sun, Oct 17, 2010, Martin Bolet wrote:
The documentation still lists the 'openssl ts' command but I couldn't find
it in the source code anymore.
It is in apps/ts.c in OpenSSL 1.0.0 and later.
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now
Yes, I was looking at 0.9.8o.
Still, I quite enjoyed the experience and would be glad to be able to
contribute. I looked into the ts app, it does not yet support HTTP
transport. Could this be a useful addition?
-Martin
2010/10/17 Dr. Stephen Henson st...@openssl.org
On Sun, Oct 17, 2010,
Even specifying a different base address doesn't fix the problem. I have a
different default address that the DLL consistently gets relocated to but
changing the preferred base address of libeay32 to that address still doesn't
work. The DLL will just get relocated to a different address.
