From: Arpadffy Zoltan <[email protected]>
> ...by using a more conventional approach SSLROOT is set correctly and ALL t=
> est PASS happily :)
I must live in some parallel universe, where none of this stuff ever
works properly. Around here (after pulling in my suggested 1.0.0
modifications to avoid the obviously broken new stuff, and to avoid
losing some useful new features) ...
test/evptests.txt seems to have gone missing, so, for me,
tests/tests.com dies prematurely:
[...]
Tests completed happily
evptests.txt: no such file or directory
An easy (no-file-copy) change to tests/tests.com can accomodate this
file's actual source location:
--- tests.com;14 2010-04-16 21:45:58 -0500
+++ tests.com;15 2010-04-16 23:07:49 -0500
@@ -21,6 +21,7 @@
$!
$ on control_y then goto exit
$ on error then goto exit
+$ on warning then goto exit ! Bad test name -> %DCL-W-USGOSUB
$!
$ if p1 .nes. ""
$ then
@@ -89,7 +90,7 @@
$ goto loop_tests
$
$ test_evp:
-$ mcr 'texe_dir''evptest' evptests.txt
+$ mcr 'texe_dir''evptest' [-.crypto.evp]evptests.txt
$ return
$ test_des:
$ mcr 'texe_dir''destest'
(The first change there ("on warning [...]") is intended to ensure
proper clean-up if the user specifies a bad test name (command-line
parameter).)
So far as I can tell, the evptest program opens its command-line
argument file for read access ("r"), so I saw no need to make a local
copy of the thing, but that could be done if anyone wished to do that
instead of using the original where it lies (in crypto/evp).
I've updated this file with these changes:
http://antinode.info/ftp/openssl/1_0_0/test/tests.com
Perhaps my environment is not obsolete enough, but I don't see the
point in having apps/openssl-vms.cnf along with apps/openssl.cnf. The
VMS C run-time stuff should have been able to cope with the UNIX-like
paths in the plain apps/openssl.cnf for some time, now. I replaced
openssl-vms.cnf with openssl.cnf, and I saw no significant difference in
the test results. Can anyone demonstrate a failure on VMS using the
UNIX-like apps/openssl.cnf file?
Also, if there's some reason to keep apps/openssl-vms.cnf, then one
of the UNIX-to-VMS path conversions therein ("certs") appears to be
defective:
@@ -327,12 +327,12 @@
[ tsa_config1 ]
# These are used by the TSA reply generation only.
-dir = ./demoCA # TSA root directory
-serial = $dir/tsaserial # The current serial number (mandatory)
+dir = sys\$disk:[.demoCA # TSA root directory
+serial = $dir]tsaserial. # The current serial number (mandatory)
crypto_device = builtin # OpenSSL engine to use for signing
signer_cert = $dir/tsacert.pem # The TSA signing certificate
# (optional)
-certs = $dir/cacert.pem # Certificate chain to include in reply
+certs = $dir.cacert.pem] # Certificate chain to include in reply
# (optional)
signer_key = $dir/private/tsakey.pem # The TSA private key (optional)
Note that "$dir/cacert.pem" is a file name, while "$dir.cacert.pem]" is
a directory. I presume that that should have been "$dir]cacert.pem".
------------------------------------------------------------------------
Steven M. Schweda s...@antinode-info
382 South Warwick Street (+1) 651-699-9818
Saint Paul MN 55105-2547
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [email protected]
Automated List Manager [email protected]
