Thomas J. Hruska wrote:
According to the FIPS 1.2 Security Policy, Appendix A, Platform 8 cannot
be built as FIPS compliant because 'x84-64 asm' is a non-existent
platform. There is no such thing as x84. It should say 'x86-64 asm'.
Validation, from what I understand, only covers those platfor
Check out the code for the OpenSSL s_client application, available in
apps/s_client.c, about how one may go about loading a client cert into
the client and attaching it to an SSL session.
Ger
On Tue, Nov 25, 2008 at 10:58 AM, vinni rathore <[EMAIL PROTECTED]> wrote:
> yes its true that server do
Is it possible to configure OpenSSL to allow the use of a non-blocking socket
? I red things about BIO* object but I am not sure if it's the good way to
do it.
Thanks.
Normand
David Schwartz wrote:
>
>
>> SSL_accept always returns < 0 error. With SSL_get_error I found that the
>> error is SSL_
Can someone point me to the user guide for FIPS 1.2. I've only been able to
find the 1.1.1 version and based on the thread below it looks like there are
some new build procedures for Windows.
Justin A wrote:
>
> Hi,
>
> Have some doubts on fips build on windows VC9. I followed the userguide
I've been working on building OpenSSL 0.9.8i on QNX 4.25, and so far it's
gone well.
I made a few changes to the config and Configure scripts, and the build ran
up to the following error:
making all in crypto/x509...
make-3.81[2]: Entering directory
`/home/cjohnson/build/openssl-build/crypto/x509'
