On 13/03/2011 18:21, Stephen Henson via RT wrote:
[j...@studt.net - Sun Mar 13 19:15:48 2011]:
Perhaps the bomb.p12 got corrupted in transit? That looks a lot like
feeding a non-ASN.1 file to openssl.
It's easy enough to recreate such a file with:
openssl pkcs12 -out foo.p12 -export
Steve
Could you explain what a private label validation is and its associated costs?
Ken
We are pleased to announce that PKWARE, Inc. (http://www.pkware.com/)
has committed to sponsor a new platform for the upcoming FIPS 140-2
validation of the OpenSSL FIPS Object Module v2.0:
HP-UX
Hello Steven,
I'm having a good time, even if no one else cares.
I do care.
I apologize for being silent, but I have been very busy with less open source
issues.
I have tested your changes on IA64 and they work well, indeed.
It was a bit tricky with the unusual extra 64 parameter for tests
On 13/03/2011 18:15, Jim Studt via RT wrote:
Perhaps the bomb.p12 got corrupted in transit? That looks a lot like
feeding a non-ASN.1 file to openssl.
This one does the same thing.
jim@rattus:~$ ls -l *.p12 ; md5sum *.p12 -rw-r--r-- 1 jim jim 718
Mar 13 12:57 bomb.p12 -rw-r--r-- 1 jim jim
Technical Support wrote:
Steve
Could you explain what a private label validation is and its associated costs?
A private label validation is when a vendor takes the code from a
source code based validation (the most recent being #1051 for the
OpenSSL FIPS Object Module v1.2.2), builds a
From: Arpadffy Zoltan zoltan.arpad...@scientificgames.se
I'm having a good time, even if no one else cares.
I do care.
I apologize for being silent, but I have been very busy with less open sour=
ce issues.
I wasn't complaining about you, but there are still some open
questions on this
I am not able to get OpenSSL to build with MinGW (from mingw.org) and
Perl (from ActiveState) installed. Both tools are available in %PATH%
and I'd like the build to run from cmd.exe (no CYGWIN bash prompt, see
below for more info). I have been working with OpenSSL 1.0.0d.
Tried using:
