OpenSSL self-test report:

OpenSSL version:  0.9.5a
Last change:      Make sure _lrotl and _lrotr are only used with MSVC....
Options:          --prefix=/dpi --openssldir=/dpi/lib/ssl
OS (uname):       SunOS zaphod 5.7 Generic_106541-07 sun4m sparc SUNW,SPARCstation-10
OS (config):      sun4m-sun-solaris2
Target (default): solaris-sparcv8-cc
Target:           solaris-sparcv8-cc
Compiler:         cc: WorkShop Compilers 5.0 98/12/15 C 5.0

Test passed.

When stunnel (3.8) was linked with openssl-0.9.5a, it always produced the
following error on start (whereas it worked with openssl-0.9.3a):
tmp_rsa_cb: error:24064064:random number generator:SSLEAY_RAND_BYTES:PRNG not seeded

Solaris has no /dev/urandom. When I faked a /dev/urandom as a symlink to some
readable file, this worked. I could reproduce the error with the following
test program, containing the same calls as stunnel:
 =============================================================================
#include <stdio.h>
#include <openssl/lhash.h>
#include <openssl/ssl.h>
#include <openssl/err.h>

#define KEYLENGTH 512
main()
{
    RSA *rsa_tmp;
    SSL_CTX *ctx;
    SSLeay_add_ssl_algorithms();
    SSL_load_error_strings();
    ctx = SSL_CTX_new(SSLv23_server_method());
    rsa_tmp = RSA_generate_key(KEYLENGTH, RSA_F4, NULL, NULL);
    if(!rsa_tmp) {
        char string[120];
        ERR_error_string(ERR_get_error(), string);
        printf("%s\n",string);
    }
}
 =============================================================================

There should be some workaround for systems without /dev/urandom !


 Hans Werner Strube
 Drittes Physikalisches Institut,  Univ. G�ttingen
 B�rgerstr. 42-44,   D-37073 G�ttingen,   Germany
 Tel.: +49-551-39-7729  Fax: +49-551-39-7720
 E-Mail: [EMAIL PROTECTED], [EMAIL PROTECTED]
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to