From: Kyle Hamilton <aerow...@gmail.com>

> Lower-case ssl_* appears to be specifically related to the
> implementation of the secure renegotiation indicator extension.  In
> any case, they are internal routines and shouldn't be exported at all,
> I should think, unless other extension parsing/adding code is
> exported.

   That sounds right.  Leaving "util/ssleay.num" unchanged seems to be
ok.  (I get carried away sometimes.)

   On the test front, there seem to be places where definitions of some
logical names and symbols seem to be assumed, but a clean environment
won't have them.  So far, I claim:

gdiff -u test/tests.com_orig test/tests.com
--- test/tests.com_orig 2009-11-13 02:45:52 -0600
+++ test/tests.com      2010-01-22 20:58:35 -0600
@@ -13,6 +13,9 @@
 $      exe_dir := sys$disk:[-.'__arch'.exe.apps]
 $
 $      set default '__here'
+$      sslroot = f$parse( "sys$disk:[-.apps];", , , , "syntax_only") - -
+        "].;"+ ".]"
+$      define /translation_attributes = concealed sslroot 'sslroot'
 $
 $      on control_y then goto exit
 $      on error then goto exit
@@ -291,5 +294,6 @@
 $
 $
 $ exit:
+$      deassign sslroot
 $      set default '__save_default'
 $      exit

   In "test/testenc.com", running openssl fails when
"crypto/bio/bss_file.c" can't find "SSLROOT:[000000]openssl.cnf", which,
I claim, is because SSLROOT is undefined.


gdiff -u test/testtsa.com_orig test/testtsa.com
--- test/testtsa.com_orig       2006-03-29 22:29:38 -0600
+++ test/testtsa.com    2010-01-22 20:34:46 -0600
@@ -3,7 +3,9 @@
 $!
 $
 $      __arch := VAX
-$      if f$getsyi("cpu") .ge. 128 then __arch := AXP
+$      if f$getsyi("cpu") .ge. 128 then -
+          __arch = f$edit( f$getsyi( "ARCH_NAME"), "UPCASE")
+$      if __arch .eqs. "" then __arch := UNK
 $      exe_dir := sys$disk:[-.'__arch'.exe.apps]
 $
 $      openssl := mcr 'f$parse(exe_dir+"openssl.exe")'

   Old/obsolete use of "AXP" instead of the new f$getsyi( "ARCH_NAME").

   Also, is there any reason to use "mcr" here instead of "$"?


   Next thing(s) I haven't looked into:

Several complaints saying:
      unable to write 'random state'
(An example appears below.)

Also:

[...]
unable to write 'random state'
writing new private key to 'tsa_key1.pem'
-----
Using configuration from [-]CATSA.CNF
Error Loading extension section TSA_CERT
2075840056:error:2006D080:BIO routines:BIO_new_file:no such 
file:ALP$DKA0:[UTILITY.SOURCE.OPENSSL.openssl-1^.0^.0-beta5.crypto.bio]bss_file.c;1:129:
2075840056:error:0E078072:configuration file routines:DEF_LOAD:no such 
file:ALP$DKA0:[UTILITY.SOURCE.OPENSSL.openssl-1^.0^.0-beta5.crypto.conf]conf_def.c;1:197:
2075840056:error:0E06D06C:configuration file routines:NCONF_get_string:no 
value:ALP$DKA0:[UTILITY.SOURCE.OPENSSL.openssl-1^.0^.0-beta5.crypto.conf]conf_lib.c;1:334:group=CA_default
 name=email_in_dn
unable to write 'random state'
[...]


   Are these problems new, or was I just not paying attention before?

------------------------------------------------------------------------

   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

Reply via email to