The test ./dsatest -app2_1 fails. It has some kind of trouble with the
PRNG. Here's the output:
./dsatest -app2_1
test generation of DSA parameters
.++++++++++++++++++++++++++++++++++++++++++++++++++*
...+........+..+...+............+.+..+......................................
....................................++++++++++++++++++++++++++++++++++++++++
+++++++++++*
seed
D5014E4B 60EF2BA8 B6211B40 62BA3224 E0427DD3
counter=105 h=2
P:
00:8d:f2:a4:94:49:22:76:aa:3d:25:75:9b:b0:68:
69:cb:ea:c0:d8:3a:fb:8d:0c:f7:cb:b8:32:4f:0d:
78:82:e5:d0:76:2f:c5:b7:21:0e:af:c2:e9:ad:ac:
32:ab:7a:ac:49:69:3d:fb:f8:37:24:c2:ec:07:36:
ee:31:c8:02:91
Q:
00:c7:73:21:8c:73:7e:c8:ee:99:3b:4f:2d:ed:30:
f4:8e:da:ce:91:5f
G:
62:6d:02:78:39:ea:0a:13:41:31:63:a5:5b:4c:b5:
00:29:9d:55:22:95:6c:ef:cb:3b:ff:10:f3:99:ce:
2c:2e:71:cb:9d:e5:fa:24:ba:bf:58:e5:b7:95:21:
92:5c:9c:c4:2e:9f:6f:46:4b:08:8c:c5:72:af:53:
e6:d7:88:02
Generate and certify a test certificate
make a certificate request using 'req'
no-rsa
Using configuration from CAss.cnf
Generating a 512 bit DSA private key
writing new private key to 'keyCA.ss'
-----
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [AU]:AU
Organization Name (eg, company) []:Dodgy Brothers
Common Name (eg, YOUR name) []:Dodgy CA
convert the certificate request into a self signed certificate using 'x509'
unable to load 'random state'
This means that the random number generator has not been seeded
with much random data.
Consider setting the RANDFILE environment variable to point at a file that
'random' data can be kept in (the file will be overwritten).
Signature ok
subject=/C=AU/O=Dodgy Brothers/CN=Dodgy CA
Getting Private key
11816:error:24064064:random number generator:SSLEAY_RAND_BYTES:PRNG not
seeded:md_rand.c:473:You need to read the OpenSSL FAQ,
http://www.openssl.org/support/faq.html
11816:error:0A06B003:dsa routines:DSA_sign_setup:BN lib:dsa_ossl.c:214:
11816:error:0A070003:dsa routines:DSA_do_sign:BN lib:dsa_ossl.c:152:
11816:error:0D072006:asn1 encoding routines:ASN1_sign:bad get asn1 object
call:a_sign.c:129:
error using 'x509' to self sign a certificate request
*** Error code 1
make: Fatal error: Command failed for target `test_ss'
Current working directory /export/home/OpenSSL/openssl-SNAP-20000731/test
*** Error code 1
make: Fatal error: Command failed for target `tests'
6:09pm cheetah: /home/OpenSSL/openssl-SNAP-20000731> echo $RANDFILE
/tmp/randomData
6:09pm cheetah: /home/OpenSSL/openssl-SNAP-20000731> dir $RANDFILE
-rw-r--r-- 1 brebey 0 Jul 31 18:05 /tmp/randomData
6:10pm cheetah: /home/OpenSSL/openssl-SNAP-20000731>
-----Original Message-----
From: Mark Mentovai [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 31, 2000 4:56 PM
To: [EMAIL PROTECTED]
Subject: Re: Support for SPARC Solaris 2.8/5.8...
Bill Rebey wrote:
>Is there a timeline for supporting SPARC Solaris 2.8?
>
>If someone wants to do the port but doesn't have an appropriate computer, I
>would be glad to set up a temporary account on our SPARC Ultra-60 so that
>the port could be done there.
What seems to be the problem in getting it to build?
Mark
--
Do not reply directly to this e-mail address
--
Mark Mentovai
UNIX Engineer
Gillette Global Network
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
