I just had a look at testtsa.com, and yeah, the corresponding shell
script has evolved since testtsa.com was last updated.  Working on it
right now.

Cheers,
Richard

In message <[email protected]> on Sun, 24 Jan 2010 23:16:59 
-0600 (CST), "Steven M. Schweda" <[email protected]> said:

sms> From: Richard Levitte <[email protected]>
sms> 
sms> > Might be a fault in test/testtsa.com...  I'll see if I can find
sms> > something there...
sms> 
sms>    I got some improvement by trying harder to preserve case in some
sms> places:
sms> 
sms> -$      call create_tsa_cert 1 tsa_cert
sms> +$      call create_tsa_cert 1 "tsa_cert"
sms> 
sms> -$      call create_tsa_cert 2 non_tsa_cert
sms> +$      call create_tsa_cert 2 "non_tsa_cert"
sms> 
sms> Knowing nothing, I'd guess that the missing "TSA_CERT" was actually
sms> supposed to be "tsa_cert".  I normally run with Parse Style: Extended,
sms> and that may make me more vulnerable to these things.  Or, it could just
sms> be lame DCL.  (Finally, there's a good reason to use:
sms>       X = "aBc"
sms> instead of:
sms>       X := aBc
sms> among other things.)
sms> 
sms> And correcting some file names:
sms> 
sms> -$              open/write file VMStsa-response1.create_tsa_cert
sms> +$              open/write file VMStsa-response_1.create_tsa_cert
sms> 
sms> -$              define/user sys$input VMStsa-response.create_tsa_cert
sms> +$              define/user sys$input VMStsa-response_1.create_tsa_cert
sms> 
sms> -$              open/write file VMStsa-response2.create_tsa_cert
sms> +$              open/write file VMStsa-response_2.create_tsa_cert
sms> 
sms> -$              define/user sys$input VMStsa-response.create_tsa_cert
sms> +$              define/user sys$input VMStsa-response_2.create_tsa_cert
sms> 
sms> Creating a file named one thing and then using a file named some other
sms> thing looked suspicious to me.
sms> 
sms>    The next problem I saw in that test:
sms> 
sms> unable to load certificates: ./tsaca.pem
sms> 
sms> seems to be an inability to find a file specified in the ".cnf" file:
sms> 
sms> certs           = $dir/tsaca.pem
sms> 
sms> The shell script seems to say things like "-out tsaca.pem -keyout
sms> tsacakey.pem", while the DCL never mentions "tsaca.pem".  Either more
sms> code theft or else less would seem to be in order here.
sms> 
sms> ------------------------------------------------------------------------
sms> 
sms>    Steven M. Schweda               s...@antinode-info
sms>    382 South Warwick Street        (+1) 651-699-9818
sms>    Saint Paul  MN  55105-2547
sms> ______________________________________________________________________
sms> OpenSSL Project                                 http://www.openssl.org
sms> Development Mailing List                       [email protected]
sms> Automated List Manager                           [email protected]

-----
Please consider sponsoring my work on free software.
See http://www.free.lp.se/sponsoring.html for details.

-- 
Richard Levitte                         [email protected]
                                        http://richard.levitte.org/

"Life is a tremendous celebration - and I'm invited!"
-- from a friend's blog, translated from Swedish
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [email protected]
Automated List Manager                           [email protected]

Reply via email to