For the morbidly curious, I may have a working LIB$INITIALIZE module for OpenSSL, which would cause it to preserve case for its command-line arguments (on modern, non-VAX systems, with SET PROCESS /PARSE_STYLE = EXTENDED). That stuff should be in:
http://antinode.info/ftp/openssl/1_0_0/apps/ Naturally, this can break some tests which had been working, and there were some other tests which have been bad for a while. Lots of updated stuff in: http://antinode.info/ftp/openssl/1_0_0/test/ After a few more changes in a few more places (and a Perl update on my system), I got part way through "test/cms-test.pl". The (a?) remaining problem there is the UNIX-like output redirection in statements like this: system("$scmd$rscmd 2>cms.err 1>cms.out"); I'm sure that that's fine if system() uses a suitable shell, but it's a loser on VMS. I'm sufficiently ignorant in Perl to know if there's some easy Perlish way around this, but, with the number of command-line arguments used here, I haven't found a convenient DCL work-around which would do the job. So far, I've changed test/cms-test.pl to identify a VMS path: --- cms-test.pl_orig 2009-11-26 16:07:28 -0600 +++ cms-test.pl 2010-04-27 08:40:05 -0500 @@ -64,6 +64,9 @@ elsif ( -f "..\\out32\\openssl.exe" ) { $ossl_path = "..\\out32\\openssl.exe"; } +elsif ( -f "SSLEXE:OPENSSL.EXE" ) { + $ossl_path = "OPENSSL"; +} else { die "Can't find OpenSSL executable"; } but I see more ".pl" files, with the same kinds of problems, and I haven't touched those yet. ------------------------------------------------------------------------ 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 openssl-dev@openssl.org Automated List Manager majord...@openssl.org